Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: "Christian Höppner" <chris@mkaito.net>, linux-btrfs@vger.kernel.org
Subject: Re: False alert: read time tree block corruption
Date: Wed, 4 Dec 2019 13:32:59 +0200
Message-ID: <6c2d09ca-1483-cd82-c906-e30731baa39f@suse.com> (raw)
In-Reply-To: <BYWL23M0PMTD.134Q4QBKEGA96@cryptbreaker>



On 4.12.19 г. 13:04 ч., Christian Höppner wrote:
> Hello,
> 
> I'm writing because the kernel wiki page relating to this error[1] says to
> write here first.
> 
> I'm (was) running Arch Linux, kernel 5.4.1, btrfs-progs 5.3.1
> 
> Yesterday during usage, the root file system remounted read-only. I was
> dumb enough to react by rebooting the machine, when I was greeted by the
> following error:
> 
> [  25.634530] BTRFS critical (device nvme0n1p2): corrupf leaf: block=810145234944...

How come you omitted exactly the most useful error that could have
pointed at the problem ? If the data is intact on-disk and the leaf
checker triggered this means you likely have faulty ram.

> [  25.634793] BTRFS error (device nvme0n1p2): block=810145234944 read time tree block corruption detected
> [  25.634961] BTRFS error (device nvme0n1p2): in __btrfs_free_extent:3080: errno=-5 IO failure
> [  25.635042] BTRFS error (device nvme0n1p2): in btrfs_run_delayed_refs:2188: errno=-5 IO failure
> [  34.653440] systemd-journald[483]: Failed to torate /var/log/journal/8f7037b10bbd4f25aadd3d19105ef920/system.journal
> 
> After booting to live media, I checked SMART, badblocks, `btrfs check
> --readonly` and `btrfs scrub`. All came back clean. I conclude that this
> is a false positive, and have downgraded the kernel to 5.3.13 as a
> workaround.
> 
> How can I provide more information to help?
> 
> [1]: https://btrfs.wiki.kernel.org/index.php/Tree-checker#How_to_handle_such_error
> 

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 11:04 Christian Höppner
2019-12-04 11:32 ` Nikolay Borisov [this message]
2019-12-05  2:50   ` Zygo Blaxell
2019-12-05 11:44   ` Christian Höppner

Reply instructions:

You may reply publically 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=6c2d09ca-1483-cd82-c906-e30731baa39f@suse.com \
    --to=nborisov@suse.com \
    --cc=chris@mkaito.net \
    --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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git