From: "Richard W.M. Jones" <rjones@redhat.com>
To: Chris Mason <chris.mason@fusionio.com>,
Chris Mason <clmason@fusionio.com>,
"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: Tue, 9 Oct 2012 08:20:02 +0100 [thread overview]
Message-ID: <20121009072002.GJ24071@rhmail.home.annexia.org> (raw)
In-Reply-To: <20121009000051.GA12735@shiny>
On Mon, Oct 08, 2012 at 08:00:51PM -0400, Chris Mason wrote:
> On Mon, Oct 08, 2012 at 03:22:30PM -0600, Richard W.M. Jones wrote:
> >
> > I have now reproduced this bug locally.
> >
> > Adding sync() + fsync of each /dev/sd* device after the mkfs command
> > does appear to fix the problem.
> >
> > However it's a little bit difficult to know for sure because I might
> > just be changing the timing of things by adding these calls.
>
> 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 (note I found an unrelated but very
serious bug in this kernel:
http://marc.info/?l=linux-kernel&m=134973394826408&w=2 )
In Fedora we apply several patches on top, but none of them
appear as if they would affect btrfs or sync/invalidate paths:
http://pkgs.fedoraproject.org/cgit/kernel.git/tree/
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
next prev parent reply other threads:[~2012-10-09 7:20 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 [this message]
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
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=20121009072002.GJ24071@rhmail.home.annexia.org \
--to=rjones@redhat.com \
--cc=chris.mason@fusionio.com \
--cc=clmason@fusionio.com \
--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).