On Sat, Jan 4, 2020 at 6:31 PM Vladimir <amigo.elite@xxxxxxxxx> wrote: > > Dear BTRFS community, > > I hit a strange issue: btrfsck unable to detect any errors, but I'm > also unable to mount this "sane" (by the btrfsck opinion) BTRFS > partition. > > Long story short: at some point, I had to forcefully power off my > laptop due to near-OOM hang with very intensive swapping caused by > starting the memory-hungry app. > This happened on 5.4.0-1.el7.elrepo.x86_64 kernel. > > After reboot I was unable to mount my data partition (/dev/stripe/data): > [29798.631579] BTRFS info (device dm-11): disk space caching is enabled > [29798.631581] BTRFS info (device dm-11): has skinny extents > [29798.637910] BTRFS info (device dm-11): bdev > /dev/mapper/stripe-data--snap2 errs: wr 0, rd 11, flush 0, corrupt > 3452, gen 0 > [29798.677872] BTRFS critical (device dm-11): corrupt leaf: > block=1651991592960 slot=16 extent bytenr=93983342592 len=524288 > invalid generation, have 140287904167864 expect (0, 6389777] > [29798.677875] BTRFS error (device dm-11): block=1651991592960 read > time tree block corruption detected What do you get for btrfs insp dump-t -b 1651991592960 /dev/ I'm not sure why the tree checker can find this problem but not btrfs check. Can you try 'btrfs check --mode=lowmem' and see if you get different results? -- Chris Murphy
