2008-01-31 22:48:39 +05:30
|
|
|
# Pass any arguments to fsck.
|
|
|
|
# By default we preen.
|
2008-02-20 06:03:38 +05:30
|
|
|
# Linux systems also force -C0 and -T.
|
|
|
|
# If fsck_args is not specified then Linux systems also use -A
|
|
|
|
# (and -R if / is rw)
|
|
|
|
#fsck_args="-p"
|
|
|
|
|
|
|
|
# We can also specify the passno in /etc/fstab to check
|
|
|
|
# If you multiplex fsck (ie ln -s fsck /etc/init.d/fsck.late) then you can
|
|
|
|
# do an fsck outside of the normal scope, say for /home.
|
2022-04-15 21:23:24 +05:30
|
|
|
# Here are some examples:-
|
2008-02-20 06:03:38 +05:30
|
|
|
#fsck_passno="=1 =2"
|
|
|
|
#fsck_passno=">1"
|
|
|
|
#fsck_passno="<2"
|
2008-01-31 22:48:39 +05:30
|
|
|
|
2011-11-23 00:26:29 +05:30
|
|
|
# If passno is not enough granularity, you can also specify mountpoints to
|
|
|
|
# check. This should NOT be used for the default non-multiplexed fsck, or your
|
|
|
|
# system might not be checked. Additionally, it is mutually exclusive with
|
|
|
|
# the fsck_passno setting.
|
|
|
|
#fsck_mnt=""
|
|
|
|
#fsck_mnt="/home"
|
|
|
|
|
2009-11-11 04:20:48 +05:30
|
|
|
# Most modern fs's don't require a full fsck on boot, but for those that do
|
2009-12-11 03:30:14 +05:30
|
|
|
# it may be advisable to skip this when running on battery.
|
2009-11-11 04:20:48 +05:30
|
|
|
# WARNING: Do not turn this off if you have any JFS partitions.
|
|
|
|
fsck_on_battery="YES"
|
|
|
|
|
2008-01-31 22:42:54 +05:30
|
|
|
# fsck_shutdown causes fsck to trigger during shutdown as well as startup.
|
2007-04-05 16:48:42 +05:30
|
|
|
# The end result of this is that if any periodic non-root filesystem checks are
|
|
|
|
# scheduled, under normal circumstances the actual check will happen during
|
|
|
|
# shutdown rather than at next boot.
|
|
|
|
# This is useful when periodic filesystem checks are causing undesirable
|
|
|
|
# delays at startup, but such delays at shutdown are acceptable.
|
2007-11-23 17:34:11 +05:30
|
|
|
fsck_shutdown="NO"
|
2015-10-25 04:25:59 +05:30
|
|
|
|
|
|
|
# fsck_abort_on_errors can be set to no to cause fsck to not abort on
|
|
|
|
# errors.
|
|
|
|
# This is useful when periodic filesystem checks are causing undesirable
|
|
|
|
# aborts.
|
|
|
|
fsck_abort_on_errors="YES"
|