linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joerg.ebertz@gmx.net
To: linux-btrfs@vger.kernel.org
Subject: Tree-Checker-Error on vServer-Directory
Date: Wed, 20 May 2020 17:54:28 +0200	[thread overview]
Message-ID: <20200520155428.GA1810@ehud.gomer.local> (raw)

Hallo,

https://btrfs.wiki.kernel.org/index.php/Tree-checker suggested that I
ask here for help.

When I run a Linux-Kernel 5.7.0-rc2, compiled with pretty much
default configuration, and try to run

  ls /vservers

I get the error message:

  ls: cannot access '/vservers': Input/output error

From dmesg I get:

  [912737.466820] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [912737.466825] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [912737.467190] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [912737.467194] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected

With kernel 5.6.9 I get:

  [  520.285953] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.285958] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.286234] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.286238] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.771733] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.771746] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.772075] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.772079] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.778309] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.778314] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.778656] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.778661] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.783287] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.783292] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.783655] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.783659] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.788400] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.788404] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.788745] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.788749] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected
  [  520.791619] BTRFS critical (device dm-2): corrupt leaf: root=5 block=350945280 slot=85 ino=55495, unknown flags detected: 0x2000000
  [  520.791624] BTRFS error (device dm-2): block=350945280 read time tree block corruption detected

With the default kernel of Debian “Stable” = “10” = “Buster”, which is
presently 4.19.0-9 this works flawlessly.  When I booted my computer
with grml 2018.12 ( https://grml.org/ ) with a 4.19.8 kernel, I didn_t
have any problems either, “btrfs check” and “btrfs scrub” didn't find
any errors.

Has there been a change to tree-checker, that has a problem with
something vServer ( http://linux-vserver.org ) does?  I don't use
vServer any more, since Debian stopped supporting it, I only keep those
files for reference.

I don't think that matters, but I have three SSDs in a RAID0 Array,
on top of which there is a LUKS container which contains a LVM2
which in turn has the BTRFS file system in one of it's LVs.

Is there any other information You need?

Greeting,
Joerg

             reply	other threads:[~2020-05-20 15:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 15:54 joerg.ebertz [this message]
2020-05-20 22:50 ` Tree-Checker-Error on vServer-Directory Qu Wenruo
2020-05-21 11:27   ` Jörg Ebertz

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=20200520155428.GA1810@ehud.gomer.local \
    --to=joerg.ebertz@gmx.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
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).