From: Liu Bo <liubo2009@cn.fujitsu.com>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Cc: Chris Mason <chris.mason@oracle.com>,
"Yan, Zheng" <zheng.z.yan@linux.intel.com>,
Josef Bacik <josef@redhat.com>, Li Zefan <lizf@cn.fujitsu.com>
Subject: [BUG] kernel BUG at fs/btrfs/relocation.c:2502!
Date: Wed, 21 Sep 2011 18:06:10 +0800 [thread overview]
Message-ID: <4E79B712.50901@cn.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]
Hi,
While running my tool(attachment), I would encounter the BUG_ON, and I FAILED to find where went wrong :(
The tool is with inode_cache option, and mainly do three things:
a. run Chris's synctest in BACKGROUND
b. create 100 snapshots
c. after b, run "btrfs fi balance"
You can follow these tips to reproduce the bug:
1) untar the attachment,
2) prepare 4 partitions, the mount point is default to /mnt,
3) $ ./2_while.sh /dev/sdb1 /dev/sdb2 /dev/sdb3 /dev/sdb4
4) then just wait several minutes and you will get the bug.
NOTE:
You MAY hit a warning and I've fixed it with this patch:
http://marc.info/?l=linux-btrfs&m=131547325515336&w=2
===
kernel BUG at fs/btrfs/relocation.c:2502!
[...]
Call Trace:
[<ffffffffa03d7a6b>] ? block_rsv_add_bytes+0x2b/0x70 [btrfs]
[<ffffffffa043292f>] relocate_tree_blocks+0x60f/0x6d0 [btrfs]
[<ffffffffa0433498>] ? add_data_references+0x248/0x260 [btrfs]
[<ffffffffa0433722>] relocate_block_group+0x272/0x620 [btrfs]
[<ffffffffa0433c83>] btrfs_relocate_block_group+0x1b3/0x2d0 [btrfs]
[<ffffffffa0413163>] btrfs_relocate_chunk+0x93/0x6a0 [btrfs]
[<ffffffff8103bfb3>] ? __wake_up+0x53/0x70
[<ffffffffa041db42>] ? btrfs_tree_read_unlock_blocking+0x42/0x70 [btrfs]
[<ffffffffa04144d2>] btrfs_balance+0x212/0x2a0 [btrfs]
[<ffffffff81152459>] ? path_openat+0x109/0x3e0
[<ffffffffa041d398>] btrfs_ioctl+0x798/0xd20 [btrfs]
[<ffffffff81112ec3>] ? handle_mm_fault+0x143/0x260
[<ffffffff81474504>] ? do_page_fault+0x1d4/0x440
[<ffffffff8115562a>] do_vfs_ioctl+0x9a/0x540
[<ffffffff81155b71>] sys_ioctl+0xa1/0xb0
[<ffffffff8147896b>] system_call_fastpath+0x16/0x1b
Code: 00 00 00 00 00 eb f6 0f 0b eb fe 0f 0b 0f 1f 84 00 00 00 00 00 eb f6 0f 0b eb fe 0f 0b 0f 1f 84 00 00 00 00 00 eb f6 0f 0b eb fe <0f> 0b 0f 1f 84 00 00 00 00 00 eb f6 48 83 7a 68 00 0f 84 eb fa
RIP [<ffffffffa0430c26>] do_relocation+0x546/0x570 [btrfs]
RSP <ffff88003c0859a8>
---[ end trace 6a4328153ff7ff17 ]---
[-- Attachment #2: TOOL.tar --]
[-- Type: application/x-tar, Size: 40960 bytes --]
next reply other threads:[~2011-09-21 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 10:06 Liu Bo [this message]
2011-09-21 10:57 ` [BUG] kernel BUG at fs/btrfs/relocation.c:2502! Yan, Zheng
2011-09-21 23:42 ` David Sterba
2011-09-22 1:42 ` Yan, Zheng
-- strict thread matches above, loose matches on Subject: below --
2011-09-21 10:07 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=4E79B712.50901@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=zheng.z.yan@linux.intel.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