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

HP-UX Handbook – Rev 13.00 Page 33 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
first mounted, it is mounted for read-only access. After fsck is run, the file system is remounted
for read/write access. The remount fails if fsck completed a resize operation or modified a file
that was opened before the fsck was run. It also fails if an I/O error occurred during the remount.
Usually, the system halts or reboots automatically.
Action:Reboot the system. The system either remounts the root cleanly or runs a full structural
fsck and remounts cleanly. If the remount succeeds, no further action is necessary. Check the
console log for I/O errors. If the disk has failed, replace it before the file system is mounted for
write access. If the system won't come up and a full structural fsck hasn't been run, reboot the
system on a backup root and manually run a full structural fsck. .
Message: 023
WARNING: msgcnt x: vxfs: mesg 023: vx_unmountroot - root file system is busy and
can't be unmounted cleanly
Explanation:
There were active files in the file system and they caused the unmount to fail. When the system
is halted, the root file system is unmounted. This happens occasionally when a process is hung
and it can't be killed before unmounting the root.
Action: fsck will run when the system is rebooted. It should clean up the file system. No other
action is necessary.
Message: 024
WARNING: msgcnt x: vxfs: mesg 024: vx_cutwait - mount_point file system current
usage table update error
Explanation: Update to the current usage table (CUT) failed. For a Version 2 disk layout, the
CUT contains a fileset version number and total number of blocks used by each fileset. The
VX_FULLFSCK flag is set in the super-block. If the super-block can't be written, the file system
is disabled.
Action: Unmount the file system and use fsck to run a full structural check.
Message: 025
WARNING: msgcnt x: vxfs: mesg 025: vx_wsuper - mount_point file system superblock
update failed
Explanation:
An I/O error occurred while writing the super-block during a resize operation. The file system is
disabled.
Action: Unmount the file system and use fsck to run a full structural check.
Check the console log for I/O errors. If the problem is a disk failure,replace the disk before the
file system is mounted for write access.