From: Josef Bacik <josef@redhat.com>
To: whirm@gmx.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/inode.c:149!
Date: Fri, 13 May 2011 14:52:22 -0400 [thread overview]
Message-ID: <4DCD7DE6.3000106@redhat.com> (raw)
In-Reply-To: <201105131919.37230.whirm@gmx.com>
On 05/13/2011 01:19 PM, whirm@gmx.com wrote:
> On Thursday 05 May 2011 20:57:17 Josef Bacik wrote:
> [..]
>> It doesn't look like that bit had my debugging output. Thanks,
>>
>> Josef
>
> Looks like the last message I sent didn't make to the list. Here's the link to
> the debug log:
>
So unfortunately I don't know how we ended up with duplicate entries in
the free space cache, but I can make it so we discard the cache if this
happens. Please try the patch I just sent to the list
[PATCH] Btrfs: check for duplicate entries in the free space cache
this will make your fs able to be mounted at the very least. I'll try
and figure out how this sort of thing happens. If you manage to make it
happen on purpose let me know how you did it so I can figure out what
I'm doing wrong. Thanks,
Josef
next prev parent reply other threads:[~2011-05-13 18:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201105051954.48405.whirm@gmx.com>
2011-05-05 18:57 ` kernel BUG at fs/btrfs/inode.c:149! Josef Bacik
2011-05-13 17:19 ` whirm
2011-05-13 18:52 ` Josef Bacik [this message]
2011-05-16 9:17 ` whirm
2011-05-16 14:11 ` Josef Bacik
2011-05-16 15:01 ` Whirm
2011-05-16 16:28 ` Josef Bacik
2011-05-23 11:57 ` Elric Milon
2011-05-23 19:51 ` Josef Bacik
2011-05-30 11:12 ` Elric Milon
2011-05-31 13:56 ` Josef Bacik
[not found] <201105051412.03175.whirm@gmx.com>
2011-05-05 17:53 ` Josef Bacik
2011-05-04 14:26 whirm
2011-05-04 14:46 ` Josef Bacik
2011-05-04 17:43 ` whirm
2011-05-04 18:21 ` Josef Bacik
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=4DCD7DE6.3000106@redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=whirm@gmx.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 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).