linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: David Sterba <dsterba@suse.cz>
Cc: polack christian <baobab874@gmail.com>,
	mailing list linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck and ctree version
Date: Mon, 28 Jan 2013 18:21:40 -0500	[thread overview]
Message-ID: <20130128232140.GA23893@shiny.globalsuite.net> (raw)
In-Reply-To: <20130128220308.GI16977@twin.jikos.cz>

On Mon, Jan 28, 2013 at 03:03:08PM -0700, David Sterba wrote:
> On Mon, Jan 28, 2013 at 03:07:13PM +0100, polack christian wrote:
> > i did use btrfsck to recover it
> > i got the tool from
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git
> > 
> > and i got this error message:
> > ...
> > Check tree block failed, want=294555648, have=0
> > Check tree block failed, want=294559744, have=0
> > Check tree block failed, want=294559744, have=0
> > btrfsck: ctree.c:1690: leaf_space_used: Assertion `!(data_len < 0)' failed.
> > Aborted (core dumped)
> > 
> > looking at
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
> 
> but this is a kernel source repository, not progs, I wonder
> 
> > this error in ctree.c have been corrected by this commit
> > 
> > http://git.kernel.org/?p=linux/kernel/git/josef/btrfs-next.git;a=commit;h=41be1f3b40b87de33cd2e7463dce88596dbdccc4
> 
> how this could happen. I have looked at the whether it does not silently
> fix a bug, nothing wrong I can see now.  How did you verify that the
> patch fixes the fsck problem?

It sounds much more like the reboot or remount cleared the cache on the
block device.

-chris


  reply	other threads:[~2013-01-28 23:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 14:07 btrfsck and ctree version polack christian
2013-01-28 22:03 ` David Sterba
2013-01-28 23:21   ` Chris Mason [this message]
     [not found]     ` <CAC6BJd=0HL2mypZ87dWk_iB69BPXYku6HzBu0J_hoCZjxXgGiQ@mail.gmail.com>
2013-01-29 16:09       ` Fwd: " polack christian
2013-01-30 11:32       ` polack christian
  -- strict thread matches above, loose matches on Subject: below --
2013-01-29 10:47 polack christian

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=20130128232140.GA23893@shiny.globalsuite.net \
    --to=chris.mason@fusionio.com \
    --cc=baobab874@gmail.com \
    --cc=dsterba@suse.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).