From: Chris Mason <chris.mason@fusionio.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Chris Mason <clmason@fusionio.com>, David Sterba <dave@jikos.cz>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Anyone seeing lots of "Check tree block failed" and other errors with latest kernel?
Date: Wed, 10 Oct 2012 15:41:13 -0400 [thread overview]
Message-ID: <20121010194113.GA687@shiny> (raw)
In-Reply-To: <20121010193853.GV24071@rhmail.home.annexia.org>
On Wed, Oct 10, 2012 at 01:38:53PM -0600, Richard W.M. Jones wrote:
> On Wed, Oct 10, 2012 at 08:38:08AM -0400, Chris Mason wrote:
> > On Tue, Oct 09, 2012 at 03:00:12AM -0600, David Sterba wrote:
> > > On Tue, Oct 09, 2012 at 08:33:57AM +0100, Richard W.M. Jones wrote:
> > > > On Tue, Oct 09, 2012 at 08:20:02AM +0100, Richard W.M. Jones wrote:
> > > > > On Mon, Oct 08, 2012 at 08:00:51PM -0400, Chris Mason wrote:
> > > > > > Ok, what's a rough idea of the mainline git equiv of the buggy kernel?
> > > > >
> > > > > On my local machine, I'm reproducing this with what Fedora calls
> > > > > 3.7.0-0.rc0.git2.4.fc19.x86_64
> > > >
> > > > OK, that's not very helpful is it :-) AFAIK it should be possible
> > > > to reproduce this with Linus's git kernel, but I haven't proven
> > > > that yet.
> > >
> > > Found the same error message in my logs with master+next:
> > >
> > > Oct 8 15:07:25 kernel: [13048.856283] device fsid cd15a893-e955-49cc-989c-4fd952a838a6 devid 1 transid 3 /dev/sda9
> > > Oct 8 15:07:25 kernel: [13048.866880] btrfs: disk space caching is enabled
> > > Oct 8 15:07:25 kernel: [13048.875767] btrfs: failed to recover relocation
> > > Oct 8 15:07:25 kernel: [13048.884662] btrfs: open_ctree failed
> > >
> > > There are some xfstests that triggered the related bug with stale data,
> > > I'm investigating further.
> >
> > Check your progs, this commit was updated to continue instead of break.
> >
> > https://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git;a=commitdiff;h=6eba9002956ac40db87d42fb653a0524dc568810;hp=bc130ecd0260e4ee6ffe07ae43fc90db281a4daa
> >
> > The original commit triggered those errors during 204.
>
> It does seem as if adding that commit to btrfs-progs fixes the
> original bug I was reporting. As before, my test isn't very reliable,
> so I cannot be 100% sure. I will continue running tests.
I didn't mention that one earlier because the git commit id in your
progs version string never had the buggy commit.
-chris
next prev parent reply other threads:[~2012-10-10 19:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 14:16 Anyone seeing lots of "Check tree block failed" and other errors with latest kernel? Richard W.M. Jones
2012-10-08 14:27 ` Chris Mason
2012-10-08 14:57 ` Richard W.M. Jones
2012-10-08 15:04 ` Chris Mason
2012-10-08 15:15 ` Richard W.M. Jones
2012-10-08 15:18 ` Chris Mason
2012-10-08 16:42 ` David Sterba
2012-10-08 17:01 ` Richard W.M. Jones
2012-10-08 21:22 ` Richard W.M. Jones
2012-10-09 0:00 ` Chris Mason
2012-10-09 7:20 ` Richard W.M. Jones
2012-10-09 7:33 ` Richard W.M. Jones
2012-10-09 9:00 ` David Sterba
2012-10-10 12:38 ` Chris Mason
2012-10-10 19:38 ` Richard W.M. Jones
2012-10-10 19:41 ` Chris Mason [this message]
2012-10-10 19:46 ` Richard W.M. Jones
2012-10-11 7:28 ` Richard W.M. Jones
2012-10-11 11:26 ` Chris Mason
2012-10-29 14:52 ` Richard W.M. Jones
2012-10-09 9:16 ` David Sterba
2012-10-09 9:26 ` Richard W.M. Jones
2012-10-10 11:49 ` Richard W.M. Jones
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=20121010194113.GA687@shiny \
--to=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--cc=dave@jikos.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=rjones@redhat.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).