On Saturday 2016-12-31 11:00, Richard Brown wrote:
Date: Sat, 31 Dec 2016 11:00:31 From: Richard Brown <RBrownCCB@opensuse.org> To: Paul Neuwirth <mail@paul-neuwirth.nl> Cc: SuSE Linux <opensuse@opensuse.org> Subject: Re: [opensuse] btrfs problem - how to run btrfsck on boot
Top-posting because I believe the information I'm about to share supercedes the majority of the other posts:
I'm shocked and somewhat disappointed that while someone linked https://btrfs.wiki.kernel.org/index.php/Btrfsck I cannot see that anyone cited the most important part:
In a nutshell, you should look at:
btrfs scrub to detect issues on live filesystems look at btrfs detected errors in syslog (look at Marc's blog above on how to use sec.pl to do this) mount -o ro,recovery to mount a filesystem with issues btrfs-zero-log might help in specific cases. Go read Btrfs-zero-log btrfs restore will help you copy data off a broken btrfs filesystem. See its page: Restore btrfs check --repair, aka btrfsck is your last option if the ones above have not worked.
Did you do all of the above before trying btrfs check --repair?
unfortunately not before. But this is good to know for the future. I am used to ext2-4 - my first option always was fsck and nearly never had problems with.
A lot of the horror stories I've seen regarding btrfs are due to misuse / abuse of btrfs far more than actual issues or bugs, and those issues that do remain need to be filed as bugs in bugzilla.opensuse.org so our Kernel team can fix them - they're very good at that, every btrfs issue I've had over the last 3 years has been robustly resolved, even bizarre edge cases where you could justifiably turn around to me and say "well don't do that, it's stupid"
;)
Hope this helps
I believe in my case btrfs did not cause these problems. data of one mdadm raid device actually was not written for a long time. after a bus reset and cache flush, data of the mirrors mismatched. Instead of repairing the array, I destroyed the fs finally using btrfsck check --repair. Now I gave btrfs with included raid1 a try. 30 / 266 GiB currently in use. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org