Re: 3.14.18 btrfs_set_item_key_safe BUG

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 16 Sep 2014 12:33:09 +0800, Daniel J Blueman wrote:

> On 3.14.18 with a BTRFS partition mounted
> noatime,autodefrag,compress=lzo, I see the second assertion in
> btrfs_set_item_key_safe() trip:
> 
> void btrfs_set_item_key_safe(struct btrfs_root *root, struct btrfs_path *path,
>                              struct btrfs_key *new_key)
> {
>         struct btrfs_disk_key disk_key;
>         struct extent_buffer *eb;
>         int slot;
> 
>         eb = path->nodes[0];
>         slot = path->slots[0];
>         if (slot > 0) {
>                 btrfs_item_key(eb, &disk_key, slot - 1);
>                 BUG_ON(comp_keys(&disk_key, new_key) >= 0);
>         }
>         if (slot < btrfs_header_nritems(eb) - 1) {
>                 btrfs_item_key(eb, &disk_key, slot + 1);
>                 BUG_ON(comp_keys(&disk_key, new_key) <= 0); <---
>         }
> 
> Full backtrace:
> 
> kernel BUG at /home/apw/COD/linux/fs/btrfs/ctree.c:3215!

This matches exactly the description mentioned just recently:
http://article.gmane.org/gmane.comp.file-systems.btrfs/38340

(not in that posting, but in the patch description).

You seem to be running a custom kernel, so try if that patch
helps. Also try nuking the free space cache when you have it
applied.

-h

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux