From: David Sterba <dsterba@suse.cz>
To: Adam Borowski <kilobyte@angband.pl>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: splat on 4.15-rc1: invalid ram_bytes for uncompressed inline extent
Date: Tue, 28 Nov 2017 15:01:20 +0100 [thread overview]
Message-ID: <20171128140120.GO3553@suse.cz> (raw)
In-Reply-To: <20171128011615.sdxutxckz67sftqm@angband.pl>
On Tue, Nov 28, 2017 at 02:16:15AM +0100, Adam Borowski wrote:
> On Tue, Nov 28, 2017 at 08:51:07AM +0800, Qu Wenruo wrote:
> > On 2017年11月27日 22:22, David Sterba wrote:
> > > On Mon, Nov 27, 2017 at 02:23:49PM +0100, Adam Borowski wrote:
> > >> On 4.15-rc1, I get the following failure:
> > >>
> > >> BTRFS critical (device sda1): corrupt leaf: root=1 block=3820662898688
> > >> slot=43 ino=35691 file_offset=0, invalid ram_bytes for uncompressed inline
> > >> extent, have 134 expect 281474976710677
> > >
> > > By a quick look at suspiciously large number
> > >
> > > hex(281474976710677) = 0x1000000000015
> > >
> > > may be a bitflip, but 0x15 does not match 134, so there could be
> > > something else involved in the corruption.
> >
> > That's a known bug, fixed by that patch which is not merged yet.
> >
> > https://patchwork.kernel.org/patch/10047489/
>
> This helped, thanks!
Patch is going to 4.15-rc2.
next prev parent reply other threads:[~2017-11-28 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 13:23 splat on 4.15-rc1: invalid ram_bytes for uncompressed inline extent Adam Borowski
2017-11-27 14:22 ` David Sterba
2017-11-28 0:51 ` Qu Wenruo
2017-11-28 1:16 ` Adam Borowski
2017-11-28 14:01 ` David Sterba [this message]
2017-11-27 15:29 ` Nikolay Borisov
2017-11-28 0:37 ` Qu Wenruo
2017-11-28 6:59 ` Nikolay Borisov
2017-11-28 7:03 ` Qu Wenruo
2017-11-28 7:05 ` Nikolay Borisov
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=20171128140120.GO3553@suse.cz \
--to=dsterba@suse.cz \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).