fsck.jfs

NAME

SYNOPSIS

DESCRIPTION

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. /dev/hdb1).

fsck.jfs must be run as root.

WARNING

fsck.jfs should not be used on a mounted file system. Using fsck.jfs on a mounted file system is very dangerous and could seriously damage the file system!

OPTIONS

-a

Autocheck mode - replay the transaction log, repair all problems automatically, and only continue fsck processing if the aggregate state is dirty. Functionally equivalent to -f:2 -c. Autocheck mode is typically the default mode used when fsck.jfs is called at boot time.

-c

After a replay of the transaction log completes successfully, only continue fsck processing if the aggregate state is dirty.

-d

Print debug statements and more details to stdout.

-fprompt_mode

Specifies the fix level that fsck will perform. Options for prompt_mode are:

:0

Do not replay the transaction log. Report errors, but do not repair them.

:1

Replay the transaction log. Report errors and prompt for permission to repair them.

:2

Replay the transaction log. Repair all errors automatically. (preen)

  If -f is not listed, the default is -f:0. If -f is listed with no prompt_mode, -f:2 is assumed.

-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 further problems).

-r

Interactive autocheck mode - replay the transaction log, prompt for permission to repair problems, and only continue fsck processing if the aggregate state is dirty. Functionally equivalent to -f:1 -c. Interactive autocheck mode is typically only used when fsck.jfs is called at boot time.

EXAMPLES

Check the 3rd partition on the 2nd hard disk, print debug information to stdout, replay the transaction log, and give permission to repair all errors:

fsck.jfs -d -f:2 /dev/hdb3

Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:

fsck.jfs -f:0 /dev/hda5

REPORTING BUGS

If you find a bug in JFS or fsck.jfs, please report it via the bug tracking system of the JFS project web site:

http://oss.software.ibm.com/developerworks/opensource/jfs/bugs

Please send as much pertinent information as possible, including the complete output of running fsck.jfs with the -d option on the JFS device.

SEE ALSO

AUTHORS

Barry Arndt  (barndt@us.ibm.com)
William Braswell, Jr.

See the JFS project web site for more details:
http://oss.software.ibm.com/developerworks/opensource/jfs/

Index

NAME

SYNOPSIS

DESCRIPTION

WARNING

OPTIONS

EXAMPLES

REPORTING BUGS

SEE ALSO

AUTHORS