On 2017-02-27 16:13, nicholas wrote:
The first thing I do with any filesystem that I suspect is broken, is fsck it. Always. On some, like XFS, that program does nothing...
fsck.btrfs also does absolutly nothing: https://btrfs.wiki.kernel.org/ index.php/Manpage/fsck.btrfs
minas-tirith:~ # cat /usr/sbin/fsck.btrfs #!/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 shift $(($OPTIND - 1)) eval DEV=\${$#} if [ ! -e $DEV ]; then echo "$0: $DEV does not exist" exit 8 fi 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'." fi exit 0 minas-tirith:~ # It looks to me copied from the XFS utility, with the difference than the later was created upstream.
if your going to use btrfs specific tools like btrfs check, you should find out how it works first.
Actually, most tools do a check and advise what to do next.
from wikipedia fsck: Full copy-on-write file systems such as ZFS and Btrfs are designed to avoid most causes of corruption and have no traditional "fsck" repair tool. Both have a "scrub" utility which examines and repairs any problems; in the background and on a mounted filesystem.
hitting your lcd monitor cause it used to work on your cathode ray tube comes to mind.
does anyone have any statistics for the number of btrfs check corruptions to know what were arguing about? 1 in 100, 1 in 10,000?
I created one partition and crashed it beyond repair on my stress test. The bug was solved, but took some long time. So, for me it was 100% casualties. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))