fsck.jfs(8) JFS utility - file system check fsck.jfs(8)
fsck.jfs - initiate replay of the JFS transaction log, and check and repair a JFS format-
fsck.jfs [ -afnopvV ] device
fsck.jfs is used to replay the JFS transaction log, check a JFS formatted device for
errors, and fix any errors found.
device is the special file name corresponding to the actual device to be checked (e.g.
fsck.jfs must be run as root.
fsck.jfs should only be used to check an unmounted file system or a file system that is
mounted READ ONLY. Using fsck.jfs to check a file system mounted other than READ ONLY
could seriously damage the file system!
If no options are selected, the default is -p.
-a Autocheck mode - Replay the transaction log. Do not continue fsck processing
unless the aggregate state is dirty or the log replay failed. Functionally equiva-
lent to -p. Autocheck mode is typically the default mode used when fsck.jfs is
called at boot time.
-f Replay the transaction log and force checking even if the file system appears
clean. Repair all problems automatically.
-n Open the file system read only. Do not replay the transaction log. Report errors,
but do not repair them.
-o Omit the replay of the transaction log. This option should not be used unless as a
last resort (i.e. the log has been severely corrupted and replaying it causes fur-
-p Automatically repair ("preen") the file system. Replay the transaction log. Do
not continue fsck processing unless the aggregate state is dirty or the log replay
failed. Functionally equivalent to -a.
-v Verbose messaging - print details and debug statements to stdout.
-V Print version information and exit (regardless of any other chosen options).
Check the 3rd partition on the 2nd hard disk, print extended information to stdout, replay
the transaction log, force complete fsck.jfs checking, and give permission to repair all
fsck.jfs -v -f /dev/hdb3
Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:
fsck.jfs -n /dev/hda5
The exit code returned by fsck.jfs represents one of the following conditions:
0 No errors
1 File system errors corrected and/or transaction log replayed successfully
2 File system errors corrected, system should be rebooted if file system was mounted
4 File system errors left uncorrected
8 Operational error
16 Usage or syntax error
128 Shared library error
If you find a bug in JFS or fsck.jfs, please report it via the bug tracking system
("Report Bugs" section) of the JFS project web site:
Please send as much pertinent information as possible, including the complete output of
running fsck.jfs with the -v option on the JFS device.
fsck(8), mkfs.jfs(8), logdump(8), logredo(8), xchklog(8), xchkdmp(8), xpeek(8)
Barry Arndt (email@example.com)
William Braswell, Jr.
fsck.jfs is maintained by IBM.
See the JFS project web site for more details:
March 1, 2002 fsck.jfs(8)