Hi Duncan, thank you for your detailed explanations! Am 23.08.2014 07:27, schrieb Duncan:
btrfs-show-super is your tool for inspecting the superblocks. See the manpage for the details. Then use btrfs rescue super-recover to overwrite the bad superblock with one that checks out as good (csum match). See the btrfs-rescue manpage for the details there.
Yes, show-super told me, that the first super block did "NOT MATCH", but the second one seemed to be in order ("MATCHED"). The SD card is 16 GiB big, so there was no third super block.
Rescue also listed the first one as bad and the second one as good and it seemed to run successfully, no errors whatsoever.
However, after "recovering", every single partition on the card broke. There were three partitions: 1 = fat32 ("/boot"), 2 = swap, 3 = btrfs ("/"). Naturally I ran the rescue command on partition 3, I hope that was not a mistake. Afterwards, as I said, none of the partitions were recognized anymore. Not even btrfs recognized the third partition.
Since I've thought I messed up entirely, I just gave up, re-formatted the card and let my backups do the job.
It's quite annoying though, how often I get those problems. May it be that the Raspberry Pi is too slow to let btrfs do its background magic, may it be that btrfs is not that suitable for SD cards (in my case it's a class 10 microSDHC, 16GiB), or may it be that btrfs is still not that reliable when it comes to "unclean" shutdowns.
Nevertheless, I will keep your explanations around for future reference, they were really helpful! Thanks again!
-- Best wishes FloGa -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
