* [BUG] kernel BUG at fs/btrfs/relocation.c:2502!
@ 2011-09-21 10:06 Liu Bo
2011-09-21 10:57 ` Yan, Zheng
0 siblings, 1 reply; 5+ messages in thread
From: Liu Bo @ 2011-09-21 10:06 UTC (permalink / raw)
To: Linux Btrfs; +Cc: Chris Mason, Yan, Zheng, Josef Bacik, Li Zefan
[-- 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* [BUG] kernel BUG at fs/btrfs/relocation.c:2502!
@ 2011-09-21 10:07 Liu Bo
0 siblings, 0 replies; 5+ messages in thread
From: Liu Bo @ 2011-09-21 10:07 UTC (permalink / raw)
To: Linux Btrfs; +Cc: Chris Mason, Josef Bacik, Li Zefan
[-- Attachment #1: Type: text/plain, Size: 1938 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 --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG] kernel BUG at fs/btrfs/relocation.c:2502!
2011-09-21 10:06 [BUG] kernel BUG at fs/btrfs/relocation.c:2502! Liu Bo
@ 2011-09-21 10:57 ` Yan, Zheng
2011-09-21 23:42 ` David Sterba
0 siblings, 1 reply; 5+ messages in thread
From: Yan, Zheng @ 2011-09-21 10:57 UTC (permalink / raw)
To: Liu Bo; +Cc: Linux Btrfs, Chris Mason, Josef Bacik, Li Zefan
On Wed, Sep 21, 2011 at 6:06 PM, Liu Bo <liubo2009@cn.fujitsu.com> wrot=
e:
>
> 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=3Dlinux-btrfs&m=3D131547325515336&w=3D2
>
> =3D=3D=3D
> kernel BUG at fs/btrfs/relocation.c:2502!
> [...]
> Call Trace:
> =A0[<ffffffffa03d7a6b>] ? block_rsv_add_bytes+0x2b/0x70 [btrfs]
> =A0[<ffffffffa043292f>] relocate_tree_blocks+0x60f/0x6d0 [btrfs]
> =A0[<ffffffffa0433498>] ? add_data_references+0x248/0x260 [btrfs]
> =A0[<ffffffffa0433722>] relocate_block_group+0x272/0x620 [btrfs]
> =A0[<ffffffffa0433c83>] btrfs_relocate_block_group+0x1b3/0x2d0 [btrfs=
]
> =A0[<ffffffffa0413163>] btrfs_relocate_chunk+0x93/0x6a0 [btrfs]
> =A0[<ffffffff8103bfb3>] ? __wake_up+0x53/0x70
> =A0[<ffffffffa041db42>] ? btrfs_tree_read_unlock_blocking+0x42/0x70 [=
btrfs]
> =A0[<ffffffffa04144d2>] btrfs_balance+0x212/0x2a0 [btrfs]
> =A0[<ffffffff81152459>] ? path_openat+0x109/0x3e0
> =A0[<ffffffffa041d398>] btrfs_ioctl+0x798/0xd20 [btrfs]
> =A0[<ffffffff81112ec3>] ? handle_mm_fault+0x143/0x260
> =A0[<ffffffff81474504>] ? do_page_fault+0x1d4/0x440
> =A0[<ffffffff8115562a>] do_vfs_ioctl+0x9a/0x540
> =A0[<ffffffff81155b71>] sys_ioctl+0xa1/0xb0
> =A0[<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 =A0[<ffffffffa0430c26>] do_relocation+0x546/0x570 [btrfs]
> =A0RSP <ffff88003c0859a8>
> ---[ end trace 6a4328153ff7ff17 ]---
>
>
call btrfs_save_ino_cache in commit_fs_roots is completely wrong.
modification to fs trees is not allowed after create_pending_snapshots(=
)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG] kernel BUG at fs/btrfs/relocation.c:2502!
2011-09-21 10:57 ` Yan, Zheng
@ 2011-09-21 23:42 ` David Sterba
2011-09-22 1:42 ` Yan, Zheng
0 siblings, 1 reply; 5+ messages in thread
From: David Sterba @ 2011-09-21 23:42 UTC (permalink / raw)
To: Yan, Zheng; +Cc: Liu Bo, Linux Btrfs, Chris Mason, Josef Bacik, Li Zefan
On Wed, Sep 21, 2011 at 06:57:56PM +0800, Yan, Zheng wrote:
> modification to fs trees is not allowed after create_pending_snapshots()
Do you have an idea whether there is a reasonable way to catch this in
code? (even if only under a config option).
david
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG] kernel BUG at fs/btrfs/relocation.c:2502!
2011-09-21 23:42 ` David Sterba
@ 2011-09-22 1:42 ` Yan, Zheng
0 siblings, 0 replies; 5+ messages in thread
From: Yan, Zheng @ 2011-09-22 1:42 UTC (permalink / raw)
To: dave, Yan, Zheng, Liu Bo, Linux Btrfs, Chris Mason, Josef
On Thu, Sep 22, 2011 at 7:42 AM, David Sterba <dave@jikos.cz> wrote:
> On Wed, Sep 21, 2011 at 06:57:56PM +0800, Yan, Zheng wrote:
>> modification to fs trees is not allowed after create_pending_snapshots()
>
> Do you have an idea whether there is a reasonable way to catch this in
> code? (even if only under a config option).
>
no idea
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-09-22 1:42 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-09-21 10:06 [BUG] kernel BUG at fs/btrfs/relocation.c:2502! Liu Bo
2011-09-21 10:57 ` 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
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.