From: "Christian Höppner" <chris@mkaito.net>
To: "Nikolay Borisov" <nborisov@suse.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: False alert: read time tree block corruption
Date: Thu, 05 Dec 2019 11:44:52 +0000 [thread overview]
Message-ID: <BYXGJQLT1XWR.HBSX91ABW4YE@cryptbreaker> (raw)
In-Reply-To: <6c2d09ca-1483-cd82-c906-e30731baa39f@suse.com>
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.
prev parent reply other threads:[~2019-12-05 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 11:04 False alert: read time tree block corruption Christian Höppner
2019-12-04 11:32 ` Nikolay Borisov
2019-12-05 2:50 ` Zygo Blaxell
2019-12-05 11:44 ` Christian Höppner [this message]
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=BYXGJQLT1XWR.HBSX91ABW4YE@cryptbreaker \
--to=chris@mkaito.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).