Hi,
I've updated my system (Debian testing) [1] several months ago (~
December) and I noticed a lot of corrupt leaf messages flooding my
kern.log [2]. Furthermore my system had some trouble, e.g.
applications were terminated after some uptime, due to the btrfs
filesystem errors. This was with kernel 5.3.
The last time I tried was with Kernel 5.6.0-1-amd64 and the problem persists.
I've downgraded my kernel to 4.19.0-8-amd64 from the Debian Stable
release and with this kernel there aren't any corrupt leaf messages
and the problem is gone. IMHO, it must be something coming with kernel
5.3 (or 5.x).
My harddisk is a SSD which is responsible for the root partition. I've
encrypted my filesystem with LUKS and just right after I entered my
password at the boot, the first corrupt leaf errors appear.
An error message looks like this:
May 7 14:39:34 foo kernel: [ 100.162145] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=35799040 slot=32, invalid root item
size, have 239 expect 439
"root=1", "slot=32", "have 239 expect 439" is always the same at every
error line. Only the block number changes.
Interestingly it's the very same as reported to the ML here [3]. I've
contacted the reporter, but he didn't have a solution for me, because
he changed to a different filesystem.
I've already tried "btrfs scrub" and "btrfs check --readonly /" in
rescue mode, but w/o any errors. I've also checked the S.M.A.R.T.
values of the SSD, which are fine. Furthermore I've tested my RAM, but
again, w/o any errors.
So, I have no more ideas what I can do. Could you please help me to
investigate this further? Could it be a bug?
Thank you very much.
Best regards,
Thorsten
1:
$ cat /etc/debian_version
bullseye/sid
$ uname -a
[no problem with this kernel]
Linux foo 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux
$ btrfs --version
btrfs-progs v5.6
$ sudo btrfs fi show
Label: 'slash' uuid: 65005d0f-f8ea-4f77-8372-eb8b53198685
Total devices 1 FS bytes used 7.33GiB
devid 1 size 115.23GiB used 26.08GiB path /dev/mapper/sda5_crypt
$ btrfs fi df /
Data, single: total=22.01GiB, used=7.16GiB
System, DUP: total=32.00MiB, used=4.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=2.00GiB, used=168.19MiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=25.42MiB, used=0.00B
2:
[several messages per second]
May 7 14:39:34 foo kernel: [ 100.162145] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=35799040 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:35 foo kernel: [ 100.998530] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=35885056 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:35 foo kernel: [ 101.348650] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=35926016 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:36 foo kernel: [ 101.619437] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=35995648 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:36 foo kernel: [ 101.874069] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=36184064 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:36 foo kernel: [ 102.339087] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=36319232 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:37 foo kernel: [ 102.629429] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=36380672 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:37 foo kernel: [ 102.839669] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=36487168 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:37 foo kernel: [ 103.109183] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=36597760 slot=32, invalid root item
size, have 239 expect 439
May 7 14:39:37 foo kernel: [ 103.299101] BTRFS critical (device
dm-0): corrupt leaf: root=1 block=36626432 slot=32, invalid root item
size, have 239 expect 439
3:
https://lore.kernel.org/linux-btrfs/19acbd39-475f-bd72-e280-5f6c6496035c@xxxxxx/
