1
.TH jfs_fsck 8 "October 29, 2002" " " "JFS utility - file system check"
5
\- initiate replay of the JFS transaction log, and check and repair a JFS formatted device
15
.B --omit_journal_replay
17
.B --replay_journal_only
24
is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any
28
is the special file name corresponding to the actual device to be checked
29
.RB (e.g. " /dev/hdb1" ).
37
should only be used to check an
39
file system or a file system that is mounted READ ONLY. Using
41
to check a file system mounted other than READ ONLY could seriously damage the file system!
45
If no options are selected, the default is
49
Autocheck mode - Replay the transaction log. Do not continue fsck processing
50
unless the aggregate state is dirty or the log replay failed. Functionally equivalent to
52
Autocheck mode is typically the default mode used when
54
is called at boot time.
57
.\" *currently unused* Perform Bad Block List utility processing only.
60
.\" After a replay of the transaction log completes successfully, only continue fsck processing if the aggregate state is dirty.
63
Replay the transaction log and force checking even if the file system appears clean. Repair all problems automatically.
65
.BI \-j " journal_device"
66
Specify the journal device.
69
Open the file system read only. Do not replay the transaction log. Report errors, but do not repair them.
71
.B \--omit_journal_replay
72
Omit the replay of the transaction log. This option should not be used unless as a last resort (i.e.
73
the log has been severely corrupted and replaying it causes further problems).
76
Automatically repair ("preen") the file system. Replay the transaction log. Do not continue fsck processing
77
unless the aggregate state is dirty or the log replay failed. Functionally equivalent to
80
.B \--replay_journal_only
81
Only replay the transaction log. Do not continue with a full file system check if the replay fails or
82
if the file system is still dirty even after a journal replay. In general, this option should only be
83
used for debugging purposes as it could leave the file system in an unmountable state. This option
87
.BR --omit_journal_replay "."
90
Verbose messaging - print details and debug statements to stdout.
93
Print version information and exit (regardless of any other chosen options).
96
Check the 3rd partition on the 2nd hard disk, print extended information to stdout, replay the transaction log,
97
force complete jfs_fsck checking, and give permission to repair all errors:
99
.B jfs_fsck \-v \-f /dev/hdb3
102
Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:
104
.B jfs_fsck \-n /dev/hda5
109
The exit code returned by
111
represents one of the following conditions:
117
File system errors corrected and/or transaction log replayed successfully
120
File system errors corrected, system should be rebooted if file system was mounted
123
File system errors left uncorrected
129
Usage or syntax error
140
please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site:
142
http://oss.software.ibm.com/jfs
145
Please send as much pertinent information as possible, including the complete output of running
149
option on the JFS device.
161
Barry Arndt (barndt@us.ibm.com)
162
William Braswell, Jr.
166
is maintained by IBM.
168
See the JFS project web site for more details:
169
http://oss.software.ibm.com/jfs
added
removed
fsck/jfs_fsck.8
