changes on mount script
0lvin at ukr.net
Sat Oct 25 07:38:49 CEST 2008
In changed mount script(lunar-init 0.1.2) used option -y for automatic repair filesystem. But this option not have standardized implementation and in some fsck have other meaning. Maybe need use -p ?
Best regards, Denis.
Options to different filesystem-specific fsck's are not standardized.
If in doubt, please consult the man pages of the filesystem-specific
checker. Although not guaranteed, the following options are supported
by most file system checkers:
-a Automatically repair the file system without any questions (use
this option with caution). Note that e2fsck(8) supports -a for
backwards compatibility only. This option is mapped to e2fsck's
-p option which is safe to use, unlike the -a option that some
file system checkers support.
-n For some filesystem-specific checkers, the -n option will cause
the fs-specific fsck to avoid attempting to repair any problems,
but simply report such problems to stdout. This is however not
true for all filesystem-specific checkers. In particular,
fsck.reiserfs(8) will not report any corruption if given this
option. fsck.minix(8) does not support the -n option at all.
-r Interactively repair the filesystem (ask for confirmations).
Note: It is generally a bad idea to use this option if multiple
fsck's are being run in parallel. Also note that this is
e2fsck's default behavior; it supports this option for backwards
compatibility reasons only.
-y For some filesystem-specific checkers, the -y option will cause
the fs-specific fsck to always attempt to fix any detected
filesystem corruption automatically. Sometimes an expert may be
able to do better driving the fsck manually. Note that not all
filesystem-specific checkers implement this option. In particu-
lar fsck.minix(8) and fsck.cramfs(8) does not support the -y
option as of this writing.
-p Automatically repair ("preen") the file system. This option will cause e2fsck to automatically fix
any filesystem problems that can be safely fixed without human intervention. If e2fsck discovers a
problem which may require the system administrator to take additional corrective action, e2fsck
will print a description of the problem and then exit with the value 4 logically or'ed into the
exit code. (See the EXIT CODE section.) This option is normally used by the system's boot
scripts. It may not be specified at the same time as the -n or -y options.
-y Assume an answer of `yes' to all questions; allows e2fsck to be used non-interactively. This
option may not be specified at the same time as the -n or -p options.
This option inhibits fsck.reiserfs from asking you for confirmation after telling you what it is
going to do. It will assuem you confirm. For safety, it does not work with the --rebuild-tree
-a, -p These options are usually passed by fsck -A during the automatic checking of those partitions
listed in /etc/fstab. These options cause fsck.reiserfs to print some information about the specified
filesystem, to check if error flags in the superblock are set and to 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 fsck.reiserfs switches to the fix-fixable mode. If the flag
indicating a fatal corruption is found set in the superblock, then fsck.reiserfs finishes with an
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 equivalent to -p. Autocheck mode is typi-
cally the default mode used when jfs_fsck is called at boot time.
-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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Lunar