From: Matthias Neuer <mneuer@web.de>
To: linux-btrfs@vger.kernel.org
Subject: invalid root item size
Date: Sun, 29 Dec 2019 14:40:18 +0100 [thread overview]
Message-ID: <19acbd39-475f-bd72-e280-5f6c6496035c@web.de> (raw)
Hi,
since I updated my system I noticed a lot of messages like the following
in dmesg (sda8 is /home).
BTRFS critical (device sda8): corrupt leaf: root=1 block=78397440
slot=32, invalid root item size, have 239 expect 439
I did a 'btrfs scrub' but it didn't find any errors. Then I started the
system in single user mode and tried 'btrfs check' but again, no error
could be found.
I read that the issue could come from bad RAM and so I ran memtest86+
for 12h but it seems my RAM is ok.
Is this a real problem and how can I fix it?
Thanks a lot,
Matthias
$ uname -a
Linux matze-debian 5.3.0-3-amd64 #1 SMP Debian 5.3.15-1 (2019-12-07)
x86_64 GNU/Linux
$ btrfs --version
btrfs-progs v5.4
# btrfs fi show
Label: none uuid: 0957d767-7f29-4235-b812-329fe851b63e
Total devices 1 FS bytes used 10.29GiB
devid 1 size 15.64GiB used 15.64GiB path /dev/sda5
Label: none uuid: 0d3f2898-446d-4967-bd54-a034108d06b9
Total devices 1 FS bytes used 12.68GiB
devid 1 size 18.62GiB used 18.61GiB path /dev/sda7
Label: none uuid: d6954ba3-3d50-4886-ae3f-a92a5ca83923
Total devices 1 FS bytes used 16.61GiB
devid 1 size 24.70GiB used 24.70GiB path /dev/sda8
# btrfs fi df /home
Data, single: total=22.67GiB, used=16.38GiB
System, DUP: total=8.00MiB, used=4.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=1.00GiB, used=236.50MiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=49.54MiB, used=0.00B
next reply other threads:[~2019-12-29 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 13:40 Matthias Neuer [this message]
2019-12-29 18:10 ` invalid root item size Chris Murphy
2019-12-29 20:10 ` Matthias Neuer
2019-12-29 22:04 ` Chris Murphy
2019-12-30 8:10 ` Matthias Neuer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19acbd39-475f-bd72-e280-5f6c6496035c@web.de \
--to=mneuer@web.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox