On Tue, Feb 16, 2021 at 10:19 AM Josef Bacik <jo...@toxicpanda.com> wrote: > > On 2/14/21 3:25 PM, Neal Gompa 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. > > > > Can anyone help? > > Can you try > > btrfs check --clear-space-cache v1 /dev/whatever > > That should fix the inode generation thing so it's sane, and then the tree > checker will allow the fs to be read, hopefully. If not we can work out some > other magic. Thanks, > > Josef
I got the same error as I did with btrfs-check --readonly... # btrfs check --clear-space-cache v1 /dev/sda3 > Opening filesystem to check... > parent transid verify failed on 796082176 wanted 888894 found 888896 > 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 -- 真実はいつも一つ！/ Always, there's only one truth!
