All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 04 May 2011 14:21:54 -0400	[thread overview]
Message-ID: <4DC19942.5010505@redhat.com> (raw)
In-Reply-To: <201105041943.31809.whirm@gmx.com>

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

On 05/04/2011 01:43 PM, whirm@gmx.com wrote:
> On Wednesday 04 May 2011 16:46:44 Josef Bacik wrote:
>> On 05/04/2011 10:26 AM, whirm@gmx.com wrote:
>>> Hi all,
>>>
>>> Here's a traceback from a failed attempt to mount a btrfs in lvm in luks
>>> filesystem.
>>>
>>> Note that if I mount it readonly it mounts successfully (haven't tried to
>>> recover any data as I have recent backups).
>>>
>>> Yesterday I defragmented both / and /home with:
>>>
>>> find /home -xdev -type f -print0 | xargs -0 sudo ./btrfs filesystem
>>> defragment -c
>>>
>>> with btrfs-tools v0.19-35-g1b444cd and rebooted a couple of times. And
>>> today I got this traceback while trying to mount home at boot time (/ is
>>> working ok)
>>>
>>> btrfsck fails with the following error:
>>>
>>> couldn't open because of unsupported option features (8).
>>> btrfsck: disk-io.c:682: open_ctree_fd: Assertion `!(1)' failed.
>>>
>>> I'm using a 2.6.39-rc5+ kernel from Linus' tree.
>>>
>>> If someone needs any extra info, just ask for it, Ill keep the corrupted
>>> filesystem for a few days before destroying it.
>>>
>>> Thanks.
>>
>> I just posted a patch for this, please try
>>
>> [PATCH] Btrfs: fix how we do space reservation for truncate
>>
>> thanks,
>>
>> Josef
>
> Still getting the same traceback when trying to mount the filesystem (see file
> attached).

Argh sorry I was looking at the wrong part of that warning.  Can you run 
with this debug patch and send me the log?  Thanks,

Josef

[-- Attachment #2: debug-free-space-cache.patch --]
[-- Type: text/plain, Size: 863 bytes --]

diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
index 1bcbe76..236a938 100644
--- a/fs/btrfs/free-space-cache.c
+++ b/fs/btrfs/free-space-cache.c
@@ -417,6 +417,8 @@ int load_free_space_cache(struct btrfs_fs_info *fs_info,
 			}
 
 			if (entry->type == BTRFS_FREE_SPACE_EXTENT) {
+				printk(KERN_ERR "adding extent [%llu-%llu]\n",
+				       e->offset, e->bytes);
 				spin_lock(&block_group->tree_lock);
 				ret = link_free_space(block_group, e);
 				spin_unlock(&block_group->tree_lock);
@@ -431,6 +433,8 @@ int load_free_space_cache(struct btrfs_fs_info *fs_info,
 					page_cache_release(page);
 					goto free_cache;
 				}
+				printk(KERN_ERR "adding bitmap [%llu-%llu]\n",
+				       e->offset, e->bytes);
 				spin_lock(&block_group->tree_lock);
 				ret = link_free_space(block_group, e);
 				block_group->total_bitmaps++;

  reply	other threads:[~2011-05-04 18:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 14:26 kernel BUG at fs/btrfs/inode.c:149! whirm
2011-05-04 14:46 ` Josef Bacik
2011-05-04 17:43   ` whirm
2011-05-04 18:21     ` Josef Bacik [this message]
     [not found] <201105051412.03175.whirm@gmx.com>
2011-05-05 17:53 ` Josef Bacik
     [not found] <201105051954.48405.whirm@gmx.com>
2011-05-05 18:57 ` 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
2011-05-30 11:12                   ` Elric Milon
2011-05-31 13:56                     ` 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=4DC19942.5010505@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 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.