I guess, btrfs aborting due to a corrupted fs is expected behavior as of now. I think, a safe way is to take snapshots regularly of your btrfs and then reverting back to the previous snapshots when something goes wrong. I will also find out more on this and update here if I do find out something more.
-- btrfsck SIGSEGVs in find_first_block_group https://bugs.launchpad.net/bugs/601877 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
