Hi! I have a strange case of a Btrfs failure.
I'm running Manjaro, btrfs-progs 4.20 # uname -a Linux unfa-desktop 4.19.30-1-MANJARO #1 SMP PREEMPT Tue Mar 19 17:49:12 UTC 2019 x86_64 GNU/Linux I've been writing data with rsync to a 3 TB Wester-Digital MyBook via USB 3.0, when accidentally, I've cut power to the disk's power brick. The result - I can't do anything with the filesystem any more. Whatever I try I get this: # btrfs check --repair --init-csum-tree /dev/sdc enabling repair mode Creating a new CRC tree Opening filesystem to check... parent transid verify failed on 1634923266048 wanted 1530 found 1532 parent transid verify failed on 1634923266048 wanted 1530 found 1532 Ignoring transid failure Couldn't setup extent tree Couldn't setup device tree ERROR: cannot open file system This is a backup drive, and I don't need it to recover, but I want to learn from this as much as possible. Power failures happen, and I want to know what to do when the same thing happens to my main production filesystem. You can read more detail here: https://unix.stackexchange.com/questions/509565/unrecoverable-btrfs-filesystem-after-a-power-failure And much more detail here: https://forum.manjaro.org/t/unfixable-btrfs-filesystem-after-a-power-failure/80994 I am writing here as I'm completely out of ideas at this point, and it seems like this is a very rare case. I was very happy to switch to Btrfs from ZFS, but now I am not so comfortable using it, if a single power failure can completely trash a filesystem beyond all repair. Or can it? -- - Tobiasz 'unfa' Karoń www.youtube.com/unfa000
