Datasheet
“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 737 — #763
i
i
i
i
i
i
i
i
C
Manual Page of reiserfsck
do, assuming yes. For safety, it does not work with
the --rebuild-tree option.
-a, -p These options are usually passed by fsck -A during
the automatic checking of those partitions listed
in /etc/fstab. These options cause reiserfsck to
print some information about the specified file
system, check if error flags in the superblock are
set and do some light-weight checks. If these
checks reveal a corruption or the flag indicating a
(possibly fixable) corruption is found set in the
superblock, then reiserfsck switches to the fix-
fixable mode. If the flag indicating a fatal cor
ruption is found set in the superblock, then reis
erfsck finishes with an error.
-V This option prints the reiserfsprogs version and
exit.
-r, -f These options are ignored.
EXPERT OPTIONS
DO NOT USE THESE OPTIONS UNLESS YOU KNOW WHAT YOU ARE
DOING. WE ARE NOT RESPONSIBLE IF YOU LOSE DATA AS A
RESULT OF THESE OPTIONS.
--no-journal-available
This option allows reiserfsck to proceed when the
journal device is not available. This option has no
effect when the journal is located on the main data
device. NOTE: after this operation you must use
reiserfstune to specify a new journal device.
--scan-whole-partition, -S
This option causes --rebuild-tree to scan the whole
partition, not only used space on the partition.
EXAMPLE OF USING
1. You think something may be wrong with a reiserfs parti
tion on /dev/hda1 or you would just like to perform a
periodic disk check.
2. Run reiserfsck --check --logfile check.log /dev/hda1.
If reiserfsck --check exits with status 0 it means no
errors were discovered.
3. If reiserfsck --check exits with status 1 (and reports
about fixable corruptions) it means that you should run
reiserfsck --fix-fixable --logfile fixable.log /dev/hda1.
4. If reiserfsck --check exits with status 2 (and reports
about fatal corruptions) it means that you need to run
reiserfsck --rebuild-tree. If reiserfsck --check fails in
737
SUSE LINUX Enterprise Server