linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [bug] balance BUG at fs/btrfs/relocation.c:886
Date: Wed, 31 Jul 2013 17:53:29 +0800	[thread overview]
Message-ID: <51F8DE99.6060704@oracle.com> (raw)


3.11.0-rc3+


------------------
[  225.586356] kernel BUG at fs/btrfs/relocation.c:886!
[  225.586362] invalid opcode: 0000 [#1] SMP
::
[  225.586431] Call Trace:
[  225.586440]  [<ffffffffa0055cd1>] ? 
btree_read_extent_buffer_pages.clone.4+0xd1/0x120 [btrfs]
[  225.586447]  [<ffffffffa00a9123>] relocate_tree_blocks+0x363/0x6d0 
[btrfs]
[  225.586454]  [<ffffffffa00a242c>] ? tree_insert+0x4c/0x60 [btrfs]
[  225.586461]  [<ffffffffa00a97b3>] relocate_block_group+0x323/0x640 
[btrfs]
[  225.586469]  [<ffffffffa00aa14f>] 
btrfs_relocate_block_group+0x19f/0x2c0 [btrfs]
[  225.586477]  [<ffffffffa0081768>] btrfs_relocate_chunk+0x88/0x770 [btrfs]
[  225.586485]  [<ffffffffa0076211>] ? read_extent_buffer+0xb1/0x110 [btrfs]
[  225.586493]  [<ffffffffa00724bf>] ? btrfs_get_token_64+0x5f/0xf0 [btrfs]
[  225.586500]  [<ffffffffa0082c51>] btrfs_balance+0x891/0xe40 [btrfs]
[  225.586508]  [<ffffffffa008c3ff>] ? kzalloc+0xf/0x20 [btrfs]
[  225.586552]  [<ffffffff8113d445>] ? __kmalloc+0xf5/0x170
[  225.586560]  [<ffffffffa008cfca>] btrfs_ioctl_balance+0x21a/0x330 [btrfs]
[  225.586568]  [<ffffffffa008fd95>] btrfs_ioctl+0x585/0x1660 [btrfs]
[  225.586575]  [<ffffffff8111d9eb>] ? handle_mm_fault+0x12b/0x230
[  225.586590]  [<ffffffff811556d4>] do_vfs_ioctl+0x84/0x4c0
[  225.586616]  [<ffffffff812867cd>] ? inode_has_perm.clone.0+0x2d/0x30
[  225.586618]  [<ffffffff8128891a>] ? file_has_perm+0x8a/0xa0
[  225.586625]  [<ffffffff8114ec71>] ? final_putname+0x21/0x50
[  225.586627]  [<ffffffff81155ba1>] SyS_ioctl+0x91/0xa0
[  225.586670]  [<ffffffff8181fed2>] system_call_fastpath+0x16/0x1b
-------------------


                 if (btrfs_root_level(&root->root_item) == cur->level) {
                         /* tree root */
                         BUG_ON(btrfs_root_bytenr(&root->root_item) !=
                                cur->bytenr);
                         if (should_ignore_root(root))
                                 list_add(&cur->list, &useless);
                         else
                                 cur->root = root;
                         break;
                 }



reproducer:

---------------------
# mkfs.btrfs /dev/sdb -f

# btrfsck --init-csum /dev/sdb
Creating a new CRC tree
Checking filesystem on /dev/sdb
UUID: 51576f7d-af1d-458b-b3c5-02eda4b3c39f
checking extents
Reinit crc root
found 0 bytes used err is 0
total csum bytes: 0
total tree bytes: 0
total fs tree bytes: 0
total extent tree bytes: 0
btree space waste bytes: 0
file data blocks allocated: 0
  referenced 0
Btrfs v0.20-rc1-413-g3f4deb0-dirty

# mount /dev/sdb /btrfs

# btrfs fi bal /btrfs
Segmentation fault
#
---------------------

  Any idea how do we fix this ?
  ( other than don't run --init-csum :-) )




             reply	other threads:[~2013-07-31  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  9:53 Anand Jain [this message]
2013-07-31 10:00 ` [bug] balance BUG at fs/btrfs/relocation.c:886 Liu Bo
2013-07-31 10:02 ` Liu Bo

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=51F8DE99.6060704@oracle.com \
    --to=anand.jain@oracle.com \
    --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).