On Fri, Jun 29, 2018 at 4:09 PM, marble <mar...@hamburg.ccc.de> wrote: > Hey, > Thanks for the quick reply :-) > >> Is there anything like unexpected power loss happens? > Power loos may have happened. It was power via a RPi. >> And would you provide the following data for debugging? >> >> # btrfs ins dump-super -fFa /dev/mapper/black > See attachment. >> And further more, what's the device mapper setup for /dev/mapper/black? >> Is there anything like RAID here? > This is due to LUKS I think. "black" is the name I gave to cryptsetup open.
No log_root* in the super. So no fsyncing at the time? What was happening at the time of the power loss? Pretty weird, all three supers are OK and yet two copies of the fs tree are corrupt. Why doesn't it fall back automatically to one of the other roots? You could try 'mount -o usebackuproot,ro' and see if that's permissive enough to succeed. I wonder if the drive firmware reordered things contrary to Btrfs expectation right at the powerfail - or even if the powerfail caused the drive firmware to do the writes in the wrong order? -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
