Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Peter Luladjiev <luladjiev@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: read time tree block corruption detected
Date: Thu, 16 Jan 2020 18:12:23 +0200
Message-ID: <6ba43f60-22d1-52da-0e9a-8561b9560481@suse.com> (raw)
In-Reply-To: <CA+ZCqs6w2Nucbght9cax9+SQ1bHitdgDtLKPA973ES8PXh1EqQ@mail.gmail.com>



On 16.01.20 г. 15:40 ч., Peter Luladjiev wrote:
> Hello,
> 
> I'm having a "read time tree block corruption detected" error after
> upgrading to kernel 5.4, reverting to kernel 5.3 fixes the problem.
> I'm using openSuse Tumbleweed, btrfs-progs v5.4

The reason is that the read-time validator got added in v5.4. 
Looking at the provided dump: 


item 70 key (1497006080 EXTENT_ITEM 4096) itemoff 11757 itemsize 37
		refs 1 gen 17889 flags DATA
		shared data backref parent 51611369472 count 1
	item 71 key (1497010176 EXTENT_ITEM 4096) itemoff 11720 itemsize 37
		refs 1 gen 17890 flags DATA
		shared data backref parent 51611369472 count 1
	item 72 key (1497014272 EXTENT_ITEM 4096) itemoff 11683 itemsize 37
		refs 1 gen 17892 flags DATA
		shared data backref parent 51611369472 count 1
	item 73 key (1497018368 EXTENT_ITEM 4096) itemoff 11646 itemsize 37
		refs 72057183177116417 gen 17894 flags DATA
		shared data backref parent 51611369472 count 1
	item 74 key (1497022464 EXTENT_ITEM 4096) itemoff 11609 itemsize 37
		refs 1 gen 17896 flags DATA
		shared data backref parent 51611369472 count 3087007745


Clearly the problematic extent has an abnormal count: 

3087007745, in binary this makes: 
10111000000000000000000000000001

so the topmost 5 bits (apart from 1) has been set to 1 whereas 
I'd assume  only the LSB (1) should be set, judging based on the the rest
of the extents that have 51611369472 as their parent. 

Can you run btrfs check on /dev/mapper/system-root and post the log here. 
Note this will be a read-only operation to you don't risk breaking
 anything. You might also have to set the --force option since this looks 
like to be your root fs which is always mounted (barring working from a rescue
disk). 

  reply index

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 13:40 Peter Luladjiev
2020-01-16 16:12 ` Nikolay Borisov [this message]
     [not found]   ` <CA+ZCqs5=N5Hdf3NxZAmPCnA8wbcJPrcH8zM-fRbt-w8tL+TjUQ@mail.gmail.com>
2020-01-17  7:34     ` Nikolay Borisov
2020-01-17  7:51       ` Peter Luladjiev
2020-01-17  7:54         ` Peter Luladjiev
2020-01-17  7:59           ` Qu Wenruo
2020-01-17  8:14           ` Nikolay Borisov
2020-01-17  8:22             ` Peter Luladjiev
2020-01-17  9:10               ` Nikolay Borisov
2020-01-17 12:04                 ` Peter Luladjiev
  -- strict thread matches above, loose matches on Subject: below --
2019-12-29 20:43 Patrick Erley
2019-12-29 22:07 ` Chris Murphy
2019-12-29 22:27   ` Patrick Erley
2019-12-29 22:32     ` Chris Murphy
2019-12-29 22:36       ` Patrick Erley
2019-12-29 23:11         ` Chris Murphy
2019-12-29 23:19           ` Patrick Erley
2019-12-29 23:24             ` Chris Murphy
2019-12-29 23:26               ` Patrick Erley
2019-12-30  0:46 ` Qu Wenruo
2019-12-30  5:36   ` Patrick Erley
2019-12-30  5:43     ` Qu Wenruo
2019-12-30  5:47       ` Patrick Erley
2019-12-30  5:50         ` Patrick Erley
2019-12-30  5:58           ` Qu Wenruo
2019-12-30  6:07             ` Patrick Erley
2019-12-30  6:09               ` Qu Wenruo
2019-12-30  8:14                 ` Patrick Erley
2019-12-30  8:54                   ` Qu Wenruo
2019-12-30  9:01                     ` Patrick Erley
2019-12-30  9:09                       ` Qu Wenruo
2019-12-30  9:21                         ` Patrick Erley
2019-12-30  9:27                           ` Qu Wenruo
2019-12-30 10:06                             ` Patrick Erley

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=6ba43f60-22d1-52da-0e9a-8561b9560481@suse.com \
    --to=nborisov@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=luladjiev@gmail.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

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