linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olivier Bonvalet <btrfs.list@daevel.fr>
To: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:5038 (linux 3.4.7)
Date: Thu, 02 Aug 2012 15:41:03 +0200	[thread overview]
Message-ID: <501A836F.90506@daevel.fr> (raw)
In-Reply-To: <20120802132259.GO17430@twin.jikos.cz>

On 02/08/2012 15:22, David Sterba wrote:
> On Wed, Aug 01, 2012 at 09:48:15PM +0200, Olivier Bonvalet wrote:
>> I have some trouble with a btrfs filesystem.
>> As you can see in logs, there is lines which are from btrfs (I
>> supposed), then some warnings at fs/btrfs/extent-tree.c, and finally a
>> "kernel BUG" at fs/btrfs/extent-tree.c:5038.
>
> Did you really see this BUG ? It comes from some unused and disabled code:
>
> 5036 #ifdef BTRFS_COMPAT_EXTENT_TREE_V0
> 5037         if (item_size<  sizeof(*ei)) {
> 5038                 BUG_ON(found_extent || extent_slot != path->slots[0]);
> ^^^^
>
> 5039                 ret = convert_extent_item_v0(trans, extent_root, path,
> 5040                                              owner_objectid, 0);
> 5041                 if (ret<  0)
> 5042                         goto abort;
> 5043
> 5044                 btrfs_release_path(path);
> 5045                 path->leave_spinning = 1;
> 5046
> 5047                 key.objectid = bytenr;
> 5048                 key.type = BTRFS_EXTENT_ITEM_KEY;
> 5049                 key.offset = num_bytes;
> 5050
> 5051                 ret = btrfs_search_slot(trans, extent_root,&key, path,
> 5052                                         -1, 1);
> 5053                 if (ret) {
> 5054                         printk(KERN_ERR "umm, got %d back from search"
> 5055                                ", was looking for %llu\n", ret,
> 5056                                (unsigned long long)bytenr);
> 5057                         btrfs_print_leaf(extent_root, path->nodes[0]);
> 5058                 }
> 5059                 if (ret<  0)
> 5060                         goto abort;
> 5061                 extent_slot = path->slots[0];
> 5062                 leaf = path->nodes[0];
> 5063                 item_size = btrfs_item_size_nr(leaf, extent_slot);
> 5064         }
> 5065 #endif
>
>
> david
>

Yes... it's a copy from my /var/log/kern.log. Is it really "disabled" ?

  reply	other threads:[~2012-08-02 13:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 19:48 kernel BUG at fs/btrfs/extent-tree.c:5038 (linux 3.4.7) Olivier Bonvalet
2012-08-02 13:22 ` David Sterba
2012-08-02 13:41   ` Olivier Bonvalet [this message]
2012-08-02 13:53     ` David Sterba
2012-08-02 16:18       ` Olivier Bonvalet
2012-08-03 22:41         ` Olivier Bonvalet
2012-08-03 23:30           ` Olivier Bonvalet
2012-08-05  8:57           ` Chris Samuel
2012-08-05 14:11             ` Olivier Bonvalet
2012-08-08 14:45               ` David Sterba
2012-08-08 16:06                 ` Stefan Behrens
2012-08-27  8:49 ` Olivier Bonvalet

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=501A836F.90506@daevel.fr \
    --to=btrfs.list@daevel.fr \
    --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).