1jfs_fsck(8) JFS utility - file system check jfs_fsck(8)
2
6 jfs_fsck - initiate replay of the JFS transaction log, and check and
7 repair a JFS formatted device
8
11 jfs_fsck [ -afnpvV ] [ -j journal_device ] [ --omit_journal_replay ] [
12 --replay_journal_only ] device
13
16 jfs_fsck is used to replay the JFS transaction log, check a JFS format‐
17 ted device for errors, and fix any errors found.
18 device is the special file name corresponding to the actual device to
20 be checked (e.g. /dev/hdb1).
21 jfs_fsck must be run as root.
23
26 jfs_fsck should only be used to check an unmounted file system or a
27 file system that is mounted READ ONLY. Using jfs_fsck to check a file
28 system mounted other than READ ONLY could seriously damage the file
29 system!
30
33 If no options are selected, the default is -p.
34 -a Autocheck mode - Replay the transaction log. Do not continue
36 fsck processing unless the aggregate state is dirty or the log
37 replay failed. Functionally equivalent to -p. Autocheck mode
38 is typically the default mode used when jfs_fsck is called at
39 boot time.
40 -f Replay the transaction log and force checking even if the file
42 system appears clean. Repair all problems automatically.
43 -j journal_device
45 Specify the journal device.
46 -n Open the file system read only. Do not replay the transaction
48 log. Report errors, but do not repair them.
49 --omit_journal_replay
51 Omit the replay of the transaction log. This option should not
52 be used unless as a last resort (i.e. the log has been severely
53 corrupted and replaying it causes further problems).
54 -p Automatically repair ("preen") the file system. Replay the
56 transaction log. Do not continue fsck processing unless the
57 aggregate state is dirty or the log replay failed. Functionally
58 equivalent to -a.
59 --replay_journal_only
61 Only replay the transaction log. Do not continue with a full
62 file system check if the replay fails or if the file system is
63 still dirty even after a journal replay. In general, this
64 option should only be used for debugging purposes as it could
65 leave the file system in an unmountable state. This option can‐
66 not be used with -f, -n, or --omit_journal_replay.
67 -v Verbose messaging - print details and debug statements to std‐
69 out.
70 -V Print version information and exit (regardless of any other cho‐
72 sen options).
73
75 Check the 3rd partition on the 2nd hard disk, print extended informa‐
76 tion to stdout, replay the transaction log, force complete jfs_fsck
77 checking, and give permission to repair all errors:
78 jfs_fsck -v -f /dev/hdb3
80 Check the 5th partition on the 1st hard disk, and report, but do not
82 repair, any errors:
83 jfs_fsck -n /dev/hda5
85
87 The exit code returned by jfs_fsck represents one of the following con‐
88 ditions:
89 0 No errors
91 1 File system errors corrected and/or transaction log replayed
93 successfully
94 2 File system errors corrected, system should be rebooted if file
96 system was mounted
97 4 File system errors left uncorrected
99 8 Operational error
101 16 Usage or syntax error
103 128 Shared library error
105
108 If you find a bug in JFS or jfs_fsck, please report it via the bug
109 tracking system ("Report Bugs" section) of the JFS project web site:
110 http://jfs.sourceforge.net/
111 Please send as much pertinent information as possible, including the
113 complete output of running jfs_fsck with the -v option on the JFS
114 device.
115
118 fsck(8), jfs_mkfs(8), jfs_fscklog(8), jfs_tune(8), jfs_logdump(8),
119 jfs_debugfs(8)
120
123 Barry Arndt (barndt@us.ibm.com)
124 William Braswell, Jr.
125 jfs_fsck is maintained by IBM.
127 See the JFS project web site for more details:
128 http://jfs.sourceforge.net/
129 October 29, 2002 jfs_fsck(8)