From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:33915 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752006AbdK1ODT (ORCPT ); Tue, 28 Nov 2017 09:03:19 -0500 Date: Tue, 28 Nov 2017 15:01:20 +0100 From: David Sterba To: Adam Borowski Cc: Qu Wenruo , linux-btrfs@vger.kernel.org Subject: Re: splat on 4.15-rc1: invalid ram_bytes for uncompressed inline extent Message-ID: <20171128140120.GO3553@suse.cz> Reply-To: dsterba@suse.cz References: <20171127132349.cm7c3mgegbqhlnrm@angband.pl> <20171127142244.GZ3553@twin.jikos.cz> <20171128011615.sdxutxckz67sftqm@angband.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <20171128011615.sdxutxckz67sftqm@angband.pl> Sender: linux-btrfs-owner@vger.kernel.org List-ID: 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.