|author||Nicholas D Steeves <firstname.lastname@example.org>||2016-04-23 00:41:30 +0100|
|committer||Nicholas D Steeves <email@example.com>||2016-04-23 00:41:30 +0100|
btrfs-progs (4.4.1-1.1) unstable; urgency=medium
* Non-maintainer upload. * New upstream release. * Rename package to btrfs-progs (Closes: #780081) * Update standards version to 3.9.7 (no changes needed). * debian/control: Add "Breaks" per Gianfranco Costamagna's suggestion * Change lintian override to reflect package rename * Switch from using postinst and postrm to using triggers per Christian Seiler's recommendation. # imported from the archive
Diffstat (limited to 'fsck.btrfs')
1 files changed, 39 insertions, 0 deletions
diff --git a/fsck.btrfs b/fsck.btrfs
new file mode 100755
@@ -0,0 +1,39 @@
+# 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!).
+while getopts ":aApy" c
+ case $c in
+ a|A|p|y) AUTO=true;;
+shift $(($OPTIND - 1))
+if [ ! -e $DEV ]; then
+ echo "$0: $DEV does not exist"
+ exit 8
+if ! $AUTO; then
+ echo "If you wish to check the consistency of a BTRFS filesystem or"
+ echo "repair a damaged filesystem, see btrfs(8) subcommand 'check'."