On Sun, Feb 14, 2021 at 4:24 PM Neal Gompa <ngomp...@gmail.com> wrote: > > On Sun, Feb 14, 2021 at 5:11 PM Chris Murphy <li...@colorremedies.com> wrote: > > > > On Sun, Feb 14, 2021 at 1:29 PM Neal Gompa <ngomp...@gmail.com> wrote: > > > > > > Hey all, > > > > > > So one of my main computers recently had a disk controller failure > > > that caused my machine to freeze. After rebooting, Btrfs refuses to > > > mount. I tried to do a mount and the following errors show up in the > > > journal: > > > > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS info (device sda3): disk > > > > space caching is enabled > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS info (device sda3): has > > > > skinny extents > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS critical (device sda3): > > > > corrupt leaf: root=401 block=796082176 slot=15 ino=203657, invalid > > > > inode transid: has 888896 expect [0, 888895] > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS error (device sda3): > > > > block=796082176 read time tree block corruption detected > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS critical (device sda3): > > > > corrupt leaf: root=401 block=796082176 slot=15 ino=203657, invalid > > > > inode transid: has 888896 expect [0, 888895] > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS error (device sda3): > > > > block=796082176 read time tree block corruption detected > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS warning (device sda3): > > > > couldn't read tree root > > > > Feb 14 15:20:49 localhost-live kernel: BTRFS error (device sda3): > > > > open_ctree failed > > > > > > I've tried to do -o recovery,ro mount and get the same issue. I can't > > > seem to find any reasonably good information on how to do recovery in > > > this scenario, even to just recover enough to copy data off. > > > > > > I'm on Fedora 33, the system was on Linux kernel version 5.9.16 and > > > the Fedora 33 live ISO I'm using has Linux kernel version 5.10.14. I'm > > > using btrfs-progs v5.10. > > > > Oh and also that block: > > > > btrfs insp dump-t -b 796082176 /dev/sda3 > > > > So, I've attached the output of the dump-s and dump-t commands. > > As for the other commands: > > # btrfs check --readonly /dev/sda3 > > Opening filesystem to check... > > parent transid verify failed on 796082176 wanted 888894 found 888896
Not good. So three different transids in play. Super says generation 888894 Leaf block says its generation is 888896, and two inodes have transid 888896 including the one the tree checker is complaining about. Somehow the super has an older generation than both what's in the leaf and what's expected. > > parent transid verify failed on 796082176 wanted 888894 found 888896 > > parent transid verify failed on 796082176 wanted 888894 found 888896 > > Ignoring transid failure > > ERROR: could not setup extent tree > > ERROR: cannot open file system > > # mount -o ro,rescue=all /dev/sda3 /mnt > > mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda3, > > missing codepage or helper program, or other error. Do you get the same kernel messages as originally reported? Or something different? -- Chris Murphy
