From: Josef Bacik <jbacik@fusionio.com>
To: Richard Cooper <richard@richardcooper.net>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck: extent-tree.c:2549: btrfs_reserve_extent: Assertion `!(ret)' failed.
Date: Thu, 3 Jan 2013 10:06:06 -0500 [thread overview]
Message-ID: <20130103150606.GC2389@localhost.localdomain> (raw)
In-Reply-To: <0400867D-6E5E-4D0F-8A06-B5AD3E58DEE6@richardcooper.net>
On Thu, Jan 03, 2013 at 05:26:38AM -0700, Richard Cooper wrote:
> Hi All,
>
> I'm trying to repair a broken fs using btrfsck and am hitting a failed assertion. I'd appreciate any suggestions for what to do next. Is there any thing I can do to help fix this bug? Any other information from my FS which would help? If the FS could be salvaged that would be a bonus, but I'm more interested in providing a useful bug report before wiping the disk.
>
Well good news is that its the allocator failing to find space for a new block,
and the allocator in btrfs-progs is under-tested, so it's likely just an
internal bug and something we can fix. Can you do btrfs fi show /dev/md4 (not
mounted) and post that so we can be sure there's actually enough space. And
I'll look at the allocator code in the meantime and see if theres something
obvious wrong. Thanks,
Josef
next prev parent reply other threads:[~2013-01-03 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 12:26 btrfsck: extent-tree.c:2549: btrfs_reserve_extent: Assertion `!(ret)' failed Richard Cooper
2013-01-03 15:06 ` Josef Bacik [this message]
2013-01-03 16:43 ` Richard Cooper
2013-01-09 10:36 ` Richard Cooper
2013-02-19 14:57 ` Richard Cooper
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=20130103150606.GC2389@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=richard@richardcooper.net \
/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.