MKMSGF
 r!u!x!{!~!
# ###&#)#,#/#2#5#8#;#>#A#D#G#J#M#P#S#V#Y#\#_#b#e#h#k#n#q#t#w#z#}#
#h$k$n$q$t$w$z$}$
jfsh.msg
HEXPLANATION: The partition being formatted is not large enough to hold a JFS
file system.
ACTION: Re-partition the disk so the partition is bigger, or format a different
partition.
HEXPLANATION: The size of the log for the JFS file system is too large.
ACTION: Specify a smaller log on the format options, or make the partition larger.
HEXPLANATION: JFS is not supported on a drive controlled by an adapter that
cannot access physical memory above 16 Megabytes.
ACTION: Upgrade the adapter or format the volume for HPFS or FAT.
HEXPLANATION: Only an LVM partition can be formatted as a JFS file system.  
The partition specified is not an LVM partition.
ACTION: Re-partition the disk so the partition is an LVM partition, or format 
a different partition.
HEXPLANATION: A critical JFS meta-data area is corrupted.  CHKDSK is unable to 
repair this meta-data area.  
ACTION: Re-FORMAT the partition, and then restore file system data from backup.
HEXPLANATION: A critical JFS meta-data area is corrupted.  CHKDSK cannot repair 
this meta-data area because it was invoked for analysis only.
ACTION: CHKDSK the partition again, using the /F parameter to grant write access
to CHKDSK.
HEXPLANATION: CHKDSK is unable to create a redundant copy of a critical JFS 
meta-data area.  If this meta-data area becomes corrupt, CHKDSK cannot repair
it without a correct redundant copy.
ACTION: Start CHKDSK with the /B parameter to clear the LVM Bad Block list.
When this completes, start CHKDSK with the /F parameter to retry this repair.
HEXPLANATION: CHKDSK is unable to create \lost+found\ on the partition and is
unable to reconnect the lost files and/or directories that it has detected.  
ACTION: Use the command MKDIR \lost+found to create the needed directory.  Then 
start CHKDSK with the /F parameter to reconnect lost files.
HEXPLANATION: The system has insufficient memory for CHKDSK to perform /F:0 
processing for this file system.  
ACTION: Start CHKDSK with the /F parameter. 
HEXPLANATION: CHKDSK is unable to create a lost+found directory in the root 
directory because the root directory already contains a non-directory object 
named lost+found.  
ACTION: Rename the existing lost+found object in root, MKDIR lost+found in the 
root directory, then run CHKDSK with the /F parameter to reconnect lost files 
and/or directories.
HEXPLANATION: At any given time, a mounted file system may have transactions 
that have been only partially written to the partition.  CHKDSK performs
its analysis by examining only the partition.  Therefore, when processing a 
mounted file system (i.e. processing /F:0), CHKDSK may report either a false
clean or a false dirty status for the partition.
ACTION: Start CHKDSK with the /F parameter.
HEXPLANATION: CHKDSK has encountered an I/O error.
ACTION: Correct the condition that caused the I/O error on the partition, and
then restart CHKDSK.
HEXPLANATION: CHKDSK was invoked with more than one  /F:n parameter
ACTION: Start CHKDSK again specifying no more than one /F:n parameter.
HEXPLANATION: CHKDSK was invoked with the /F:n parameter where n is not valid.
ACTION: For analysis only, start CHKDSK with no /F:n parameter or with the /F:0
parameter.  For analysis and repair, start CHKDSK with the /F parameter or with
the /F:n parameter where 1<=n<=3.
HEXPLANATION: CHKDSK was invoked with a parameter that is not supported for 
this file system.
ACTION: Start CHKDSK again, without the invalid parameter.
HEXPLANATION: The journal log is damaged.  CHKDSK's attempts to reformat it have 
failed because of an I/O error.  This condition does not prevent CHKDSK from 
performing analysis and repairs to other areas of the file system.
ACTION: Correct the condition that caused the I/O error on the partition, and
then restart CHKDSK.
HEXPLANATION: CHKDSK is unable to verify and/or refresh the contents of the 
partition's boot sector because of an I/O error.  This condition does not prevent 
CHKDSK from performing analysis and repair to other areas of the file system, but 
might prevent the system from recognizing the partition as a JFS file system.
ACTION: If the partition is not recognized as a JFS file system during subsequent
processing, correct the condition which caused the I/O error on the partition, then
start CHKDSK with /F to retry.
HEXPLANATION: CHKDSK has encountered an I/O error.
ACTION: Correct the condition which caused the I/O error on the partition, and then 
restart CHKDSK.
HEXPLANATION: CHKDSK has encountered an I/O error.
ACTION: Correct the condition that caused the I/O error on the partition, and
then restart CHKDSK.
HEXPLANATION: CHKDSK has encountered an I/O error.
ACTION: Correct the condition that caused the I/O error on the partition, and
then restart CHKDSK.
HEXPLANATION: CHKDSK has encountered an error which prevents it from 
completing the requested process.  If a repair or refresh has been partially
written to the partition, the partition is left in an unaccessible state.
ACTION: If the partition has been left in an unaccessible state, correct the
condition that caused the error, then restart CHKDSK.  If it is not possible to
correct the condition causing the error, re-FORMAT the partition, and then
restore file system data from backup.
HEXPLANATION: The LVM bad block table for this partition more than 50 percent full.  
To relieve this situation, CHKDSK can transfer entries from the LVM table that is
fixed in length to the JFS table that has no size limit.  CHKDSK performs this 
function while the file system is active.
ACTION: Start CHKDSK with the /B parameter to transfer entries from the LVM
table to the JFS table.
HEXPLANATION: CHKDSK is transferring entries from the LVM bad block table for 
this partition that is fixed in length to the JFS table that has no size limit.  
CHKDSK performs this function while the file system is active.
HEXPLANATION: JFS CHKDSK has encountered an internal processing error.  CHKDSK 
cannot continue processing this file system.
ACTION: Record the message, and then contact IBM support.
HEXPLANATION: JFS CHKDSK is unable to obtain write access to the file system at
this time. 
ACTION: If some other process has the file system locked for exclusive write access,
run CHKDSK /B again when that process completes.  If no other process has the
file system locked, run CHKDSK with the /F parameter to correct the file system.
Note: /F processing includes /B processing.
HEXPLANATION: A critical JFS meta-data area is corrupted.
ACTION: Start CHKDSK with the /F parameter.
HEXPLANATION: The integrity of the file system is in doubt.
ACTION: Start CHKDSK with the /F parameter.
HEXPLANATION: JFS DEFRAGFS has encounted an unexpected error.  Processing
cannot continue.
ACTION: Record the message, and then contact IBM support..