linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Josef Bacik <JBacik@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/volumes.c:3707 still not fixed in 3.7.1 (btrfs-zero-log required) but shown as "RIP btrfs_num_copies"
Date: Fri, 11 Jan 2013 09:49:52 -0500	[thread overview]
Message-ID: <20130111144952.GA1876@localhost.localdomain> (raw)
In-Reply-To: <20130110162009.GF16943@merlins.org>

On Thu, Jan 10, 2013 at 09:20:09AM -0700, Marc MERLIN wrote:
> On Tue, Jan 08, 2013 at 10:46:03AM -0800, Marc MERLIN wrote:
> > On Tue, Jan 08, 2013 at 01:25:41PM -0500, Josef Bacik wrote:
> > > On Tue, Jan 08, 2013 at 09:49:58AM -0700, Marc MERLIN wrote:
> > > > Unfortunately my laptop deadlocks from time to time, and too often
> > > > it triggers this bug in btrfs which is quite hard to recover from.
> > > > 
> > > 
> > > You are getting bad tree blocks which really isn't the tree logs fault.  Can you
> > > scrub your file system and make sure there's not some sort of latent issue going
> > > on?  And if you have problems again please try btrfs-next as I've fixed a few
> > > log replay bugs recently.  Thanks,
> > 
> > Thanks for your answer.
> > 
> > I've only read about scrub in a mirorr situation, as per
> > https://blogs.oracle.com/wim/entry/btrfs_scrub_go_fix_corruptions
> > 
> > It's a single device here, so if there are problems, I'm not sure how scrub
> > will be able to fix them.
> > Would you like me to go ahead and do it anyway?
> > 

Well its mostly to verify you have some sort of latent corruption sitting
around.  If you have DUP it will be able to fix it, but if you don't we'll at
least know something else is wrong and we can try and work out if fsck will fix
it.

> > And before I further remove potential debug state
> > 1) what about this problem?
> > btrfs-image: btrfs-image.c:518: create_metadump: Assertion `!(ret < 0)'
> > failed.
> > Aborted

Probably just related to whatever corruption it is you are seeing.

> > 
> > 2) anything else you want me to get off my filesystem before I scrub it?

Nope, hopefully it should be non-destructive.  Thanks,

Josef

  reply	other threads:[~2013-01-11 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 16:49 kernel BUG at fs/btrfs/volumes.c:3707 still not fixed in 3.7.1 (btrfs-zero-log required) but shown as "RIP btrfs_num_copies" Marc MERLIN
2013-01-08 17:10 ` Hugo Mills
2013-01-08 18:09   ` Marc MERLIN
2013-01-14  6:28   ` Marc MERLIN
2013-01-08 18:25 ` Josef Bacik
2013-01-08 18:46   ` Marc MERLIN
2013-01-10 16:20     ` Marc MERLIN
2013-01-11 14:49       ` Josef Bacik [this message]
2013-01-13  3:12         ` Marc MERLIN
2013-01-17 11:31           ` David Sterba
2013-01-17 14:16             ` Marc MERLIN

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=20130111144952.GA1876@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.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).