HP-UX HB v13.00 Ch-14 - JFS

HP-UX Handbook – Rev 13.00 Page 26 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
/var/adm/messages.
In some cases, additional data is written to the kernel buffer. For example, if an inode is marked
bad, the contents of the bad inode is written. When an error message is displayed on the console,
you can use the unique message ID to find the message in /var/adm/messages and obtain the
additional information.
Message: 001
NOTICE: msgcnt x: vxfs: mesg 001: vx_nospace - mount_point file system full (n block extent)
Explanation:
The file system is out of space. Often, there is plenty of space and one runaway process used up
all the remaining free space. In other cases, the available free space becomes fragmented and
unusable for some files.
Action: Monitor the free space in the file system and prevent it from becoming full. If a
runaway process has used up all the space, stop that process, find the files created by the process,
and remove them. If the file system is out of space, remove files, defragment, or expand the file
system.
To remove files, use the find command to locate the files that are to be removed. To get the most
space with the least amount of work, remove large files or file trees that are no longer needed.
To defragment or expand the file system, use fsadm (see the fsadm(1M) manual page).
Message: 002
WARNING: msgcnt x: vxfs: mesg 002:vx_snap_strategy - mount_point file system write
attempt to read-only file system
WARNING: msgcnt x: vxfs: mesg 002: vx_snap_copyblk - mount_point file system write
attempt to read-only file system
Explanation:
The kernel tried to write to a read-only file system. This is an unlikely problem, but if it occurs,
the file system is disabled.
Action: The file system was not written, so no action is required. Report this as a bug to your
customer support organization.
Message: 003, 004, 005
WARNING: msgcnt x: vxfs: mesg 003: vx_mapbad - mount_point file system free extent
bitmap in au aun marked bad
WARNING: msgcnt x: vxfs: mesg 004: vx_mapbad - mount_point file system free inode
bitmap in au aun marked bad
WARNING: msgcnt x: vxfs: mesg 005: vx_mapbad - mount_point file system inode
extended operation bitmap in au aun marked bad
Explanation:
If there is an I/O failure while writing a bitmap, the map is marked bad. The kernel considers the
maps to be invalid, so does not do any more resource allocation from maps. This situation can
cause the file system to report "out of space" or "out of inode" error messages even though df
may report an adequate amount of free space. This error may also occur due to bitmap
inconsistencies. If a bitmap fails a consistency check, or blocks are freed that are already free in