From: Josef Bacik <josef@redhat.com>
To: Elric Milon <whirm@gmx.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/inode.c:149!
Date: Mon, 23 May 2011 15:51:57 -0400 [thread overview]
Message-ID: <4DDABADD.7090209@redhat.com> (raw)
In-Reply-To: <201105231357.41588.whirm@gmx.com>
On 05/23/2011 07:57 AM, Elric Milon wrote:
> On Monday 16 May 2011 18:28:49 you wrote:
>> On 05/16/2011 11:01 AM, Whirm wrote:
>>> On Monday 16 May 2011 16:11:19 Josef Bacik wrote:
>
>>>
>>> Sorry yes, I meant this is how I managed to get the corrupted filesystem.
>>>
>>> Ill try to break it again.
>>
>> Oh ok perfect, yeah I will try and do the same sort of things and see if
>> I can get it to happen as well. Thanks,
>
> Great, btw, I tried to see if I can mount the corrupted filesystem with
> the patch you told me about applied, and it fails, here's the log:
>
> http://pastebin.com/raw.php?i=4Kfv927B
>
> That happens using 2.6.39-rc7+ from git with the following patch applied (its
> the debug patch and the possible fix you told me about):
>
Ok so this is a different kind of corruption, wooo! Can you apply this
debug patch and get me the output so we can try and fix this bit? Thanks,
Josef
diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
index cd5e82e..54a8df5 100644
--- a/fs/btrfs/file.c
+++ b/fs/btrfs/file.c
@@ -365,6 +365,9 @@ next_slot:
extent_end = key.offset +
btrfs_file_extent_inline_len(leaf, fi);
} else {
+ printk(KERN_ERR "Weird entry at slot=%d, type=%lu\n",
+ path->slots[0], extent_type);
+ btrfs_print_leaf(root, leaf);
WARN_ON(1);
extent_end = search_start;
}
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index dc8fb2b..f951053 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -145,6 +145,9 @@ static noinline int insert_inline_extent(struct
btrfs_trans_handle *trans,
inode_add_bytes(inode, size);
ret = btrfs_insert_empty_item(trans, root, path, &key,
datasize);
+ if (ret)
+ printk(KERN_ERR "ret=%d, inode=%d, start=%llu, size=%llu\n",
+ ret, inode->i_ino, start, size);
BUG_ON(ret);
if (ret) {
err = ret;
next prev parent reply other threads:[~2011-05-23 19:51 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
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 [this message]
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=4DDABADD.7090209@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).