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: Thu, 11 Oct 2012 07:26:28 -0400 [thread overview]
Message-ID: <20121011112628.GE687@shiny> (raw)
In-Reply-To: <20121011072821.GA4605@rhmail.home.annexia.org>
On Thu, Oct 11, 2012 at 01:28:21AM -0600, Richard W.M. Jones wrote:
> Well the bad news is that the bug happened again overnight, even
> though we were definitely using btrfs-progs with the 6eba90029 patch
> added, _and_ it was doing a sync + fsync between the mkfs and the
> mount.
This is good just because it makes the most sense. The only thing worse
than a bug is a bug that disappears for the wrong reasons ;)
>
> Here is the log:
> [ 17.943272] btrfs bad tree block start 0 135168
> [ 17.955270] btrfs: open_ctree failed
This is also good because it really points to the invalidate. You've
got zeros where we wrote 135168, and pretty much the only way to get
zeros on a disk block is if the kernel did a memset. Sure some app
could have written the zeros there, but that block offset is unlikely to
get allocated as a data block by the other filesystems.
So, I'll go back to the invalidate code ;)
-chris
next prev parent reply other threads:[~2012-10-11 11:26 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
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 [this message]
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=20121011112628.GE687@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.