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

HP-UX Handbook – Rev 13.00 Page 25 (of 47)
Chapter 14 Journaled File System (JFS)
October 29, 2013
check the syslog for I/O errors.
JFS Error Codes
Most messages can appear in one of two forms. The first form applies to the file system in
general. The second form is specific to the structural file set within the file system.
Messages of the second form contain the string (structural) to indicate that they occurred in the
structural file set.
These errors are categorized in the following areas:
 File System Response to Problems
 Marking an Inode Bad
 Disabling Transactions
 Disabling the File System
 Recovering a Disabled File System
 Kernel Messages
 Global Message IDs
Recovering a Disabled File System
When the file system is disabled, no data can be written to the disk. Although some minor file
system operation still work, most simply return EIO. The only thing that can be done when the
file system is disabled is to do a umount and run a full fsck.
Although a log replay may produce a clean file system, do a full structural check to be safe.
To do a full structural check, use the following example :
# fsck -F vxfs -o full, nolog -y /dev/rdsk/c1t0d0s1
The file system usually becomes disabled because of disk errors.
Disk failures that disabled a file system should be fixed as quickly as possible (see
fsck_vxfs(1M)).
VxFS Kernel Messages
This section lists the VxFS kernel error messages in numerical order.
The Explanation sub-section for each message describes the problem.
The Action sub-section suggests possible solutions.
Global Message IDs
Each time a VxFS kernel message is displayed on the system console, it is displayed along with a
monatomically increasing message ID, shown in the msgcnt field. This ID guarantees that the
sequence of events is known in order to help analyze file system problems.
Each message is also written to an internal kernel buffer and can be viewed in the file