6f0a14303f
Harald suggested that we remove the message from the fake fsck.btrfs that some distros run at boot: https://bugzilla.redhat.com/show_bug.cgi?id=1206502 "This output does not add anything, but is a disturbing element of booting up a system. It's the only message I get, when starting my system, before gdm is started." I'm inclined to agree. This makes the tiniest change to remove the message that's output for an auto invocation. My guess is that it was just copied from the xfs fsck.xfs and that no one actually cares about it. Signed-off-by: Zach Brown <zab@zabbo.net> Signed-off-by: David Sterba <dsterba@suse.cz>
39 lines
1.1 KiB
Bash
Executable file
39 lines
1.1 KiB
Bash
Executable file
#!/bin/sh -f
|
|
#
|
|
# Copyright (c) 2013 SUSE
|
|
#
|
|
# copied from fsck.xfs
|
|
# Copyright (c) 2006 Silicon Graphics, Inc. All Rights Reserved.
|
|
#
|
|
|
|
# fsck.btrfs is a type of utility that should exist for any filesystem and is
|
|
# called during system setup when the corresponding /etc/fstab entries contain
|
|
# non-zero value for fs_passno. (See fstab(5) for more.)
|
|
#
|
|
# Traditional filesystems need to run their respective fsck utility in case the
|
|
# filesystem was not unmounted cleanly and the log needs to be replayed before
|
|
# mount. This is not needed for BTRFS. You should set fs_passno to 0.
|
|
#
|
|
# If you wish to check the consistency of a BTRFS filesystem or repair a
|
|
# damaged filesystem, see btrfs(8) subcommand 'check'. By default the
|
|
# filesystem consistency is checked, the repair mode is enabled via --repair
|
|
# option (use with care!).
|
|
|
|
AUTO=false
|
|
while getopts ":aApy" c
|
|
do
|
|
case $c in
|
|
a|A|p|y) AUTO=true;;
|
|
esac
|
|
done
|
|
eval DEV=\${$#}
|
|
if [ ! -e $DEV ]; then
|
|
echo "$0: $DEV does not exist"
|
|
exit 8
|
|
fi
|
|
if [ "$AUTO" == "false" ]; then
|
|
echo "If you wish to check the consistency of a BTRFS filesystem or"
|
|
echo "repair a damaged filesystem, see btrfs(8) subcommand 'check'."
|
|
fi
|
|
exit 0
|