linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Chris Mason <chris.mason@fusionio.com>,
	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: Mon, 29 Oct 2012 14:52:45 +0000	[thread overview]
Message-ID: <20121029145245.GA3346@rhmail.home.annexia.org> (raw)
In-Reply-To: <20121011112628.GE687@shiny>

On Thu, Oct 11, 2012 at 07:26:28AM -0400, Chris Mason wrote:
> 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 ;)

Any luck on this?  It's still happening in the latest kernels.  If
there's anything / patch you want me to try, let me know.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

  reply	other threads:[~2012-10-29 14:52 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
2012-10-29 14:52                               ` Richard W.M. Jones [this message]
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=20121029145245.GA3346@rhmail.home.annexia.org \
    --to=rjones@redhat.com \
    --cc=chris.mason@fusionio.com \
    --cc=clmason@fusionio.com \
    --cc=dave@jikos.cz \
    --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).