Re: False alert: read time tree block corruption

Christian Höppner
2019-12-05T11:44:56Z

On Wed Dec 4, 2019 at 1:32 PM, Nikolay Borisov wrote:
> How come you omitted exactly the most useful error that could have
> pointed at the problem ?

My bad. Here's the full text:

:: running early hook [udev]
Starting version 244-1-arch
:: running hook [udev]
:: Triggering uevents...
[ 4.474941] hid-generic 003:0D8C:0005.0001: No inputs registered, leaving
:: performing fsck on '/dev/nvme0n1p2'
:: mounting '/dev/nvme0n1p2' on real root
[ 6.153174] BTRFS critical (device nvme0n1p2): corrupt leaf: block=209407475712 slot=110 extent bytenr=224368013312 len=262144 invalid generation, have 94071693158288 expect (0 3890273]
[ 6.153252] BTRFS error (device nvme0n1p2): block=209407475712 read time tree corruption detected
[ 6.153421] BTRFS critical (device nvme0n1p2): corrupt leaf: block=209407475712 slot=110 extent bytenr=224368013312 len=262144 invalid generation, have 94071693158288 expect (0 3890273]
[ 6.153462] BTRFS error (device nvme0n1p2): block=209407475712 read time tree corruption detected
[ 6.153495] BTRFS error (device nvme0n1p2): failed to read block groups: -5
[ 6.230015] BTRFS error (device nvme0n1p2): open_ctree failed
mount: /new_root: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2, missing codepage or helper program, or other error.
You are being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#

> If the data is intact on-disk and the leaf
> checker triggered this means you likely have faulty ram.

The data on disk seems fine. System boots with kernel 5.3.13, `btrfs
scrub` and `btrfs check --readonly` report no errors, nor have there
been any further issues during normal usage.

I'll run memtest overnight and report back.