On Mon, Nov 16, 2009 at 2:55 PM, Gong, Zhipeng <zhipeng.gong@intel.com>
wrote:> The kernel oops can be reproduced with these steps steadily:
> dd if=/dev/zero of=img0 bs=1k count=262144
> dd if=/dev/zero of=img1 bs=1k count=262144
> losetup /dev/loop0 img0
> losetup /dev/loop1 img1
> mkfs.btrfs -m raid0 /dev/loop0 /dev/loop1
> mkdir btrfs
> mount -t btrfs /dev/loop0 btrfs
> #create some files on btrfs
> btrfs-vol -r /dev/loop1 btrfs
>
> Regards
> Zhipeng
> =====================================================> [ 519.625326]
btrfs allocation failed flags 2, wanted 4096
> [ 519.625334] space_info has 4128768 free, is not full
> [ 519.625342] space_info total=4194304, pinned=0, delalloc=0, may_use=0,
used=0, root=0, super=65536, reserved=0
> [ 519.625350] block group 0 has 4194304 bytes, 0 used 0 pinned 0 reserved
> [ 519.625357] entry offset 4096, bytes 61440, bitmap no
> [ 519.625364] entry offset 131072, bytes 4063232, bitmap no
> [ 519.625370] block group has cluster?: no
> [ 519.625374] 2 blocks of free space at or bigger than bytes is
> [ 519.625395] ------------[ cut here ]------------
> [ 519.625401] kernel BUG at fs/btrfs/volumes.c:2389!
> [ 519.625407] invalid opcode: 0000 [#1] PREEMPT SMP
> [ 519.625417] last sysfs file:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/PNP0C0A:00/power_supply/BAT1/charge_full
> [ 519.625424] Modules linked in: uvcvideo battery joydev
> [ 519.625436]
> [ 519.625444] Pid: 1079, comm: btrfs-vol Not tainted
(2.6.32.rc5-72.2.moblin2-netbook #1) Inspiron 910
> [ 519.625451] EIP: 0060:[<c11450e7>] EFLAGS: 00010286 CPU: 1
> [ 519.625464] EIP is at __finish_chunk_alloc+0x77/0x202
> [ 519.625470] EAX: ffffffe4 EBX: deed8500 ECX: 00000000 EDX: 0000002c
> [ 519.625476] ESI: 04000000 EDI: 00000000 EBP: dc995c54 ESP: dc995bf8
> [ 519.625483] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> [ 519.625491] Process btrfs-vol (pid: 1079, ti=dc994000 task=ef9092d0
task.ti=dc994000)
> [ 519.625496] Stack:
> [ 519.625500] 00000000 00000000 e5de4800 00000001 e2c5aea4 e5d99000
00000000 e5c7c56c
> [ 519.625517] <0> e5de4800 00000050 ef9823c0 04000000 00000000
cf3720e4 07c00000 00000000
> [ 519.625535] <0> 00000000 00000000 f6914dc8 f6914dc8 e5de4800
e2c5aea4 0000000a dc995c98
> [ 519.625554] Call Trace:
> [ 519.625565] [<c1146ea7>] ? btrfs_alloc_chunk+0x6f/0x81
> [ 519.625576] [<c1118250>] ? do_chunk_alloc+0x1d5/0x228
> [ 519.625587] [<c111f036>] ?
btrfs_prepare_block_group_relocation+0x103/0x12b
> [ 519.625598] [<c1159059>] ? btrfs_relocate_block_group+0x11e/0x357
> [ 519.625607] [<c114564b>] ? btrfs_relocate_chunk+0x57/0x432
> [ 519.625618] [<c113d4c5>] ? map_private_extent_buffer+0xe7/0x109
> [ 519.625628] [<c1135adf>] ?
btrfs_dev_extent_chunk_offset+0x5c/0xa9
> [ 519.625638] [<c113d190>] ? unmap_extent_buffer+0xc/0xe
> [ 519.625646] [<c1135b20>] ?
btrfs_dev_extent_chunk_offset+0x9d/0xa9
> [ 519.625655] [<c1145c0e>] ? btrfs_shrink_device+0x1e8/0x2f3
> [ 519.625666] [<c114626a>] ? btrfs_rm_device+0x1fe/0x44e
> [ 519.625677] [<c108a9c3>] ? memdup_user+0x2c/0x43
> [ 519.625685] [<c114a48a>] ? btrfs_ioctl+0x73c/0x8aa
> [ 519.625695] [<c107b9a2>] ? filemap_fault+0xc9/0x34d
> [ 519.625704] [<c107b4b0>] ? unlock_page+0x3e/0x41
> [ 519.625713] [<c1149d4e>] ? btrfs_ioctl+0x0/0x8aa
> [ 519.625723] [<c10ad7f2>] ? vfs_ioctl+0x18/0x71
> [ 519.625731] [<c10addc0>] ? do_vfs_ioctl+0x4d6/0x514
> [ 519.625741] [<c10a186c>] ? fd_install+0x44/0x4a
> [ 519.625750] [<c10ade2c>] ? sys_ioctl+0x2e/0x48
> [ 519.625760] [<c10029a1>] ? syscall_call+0x7/0xb
> [ 519.625765] Code: 2f e9 a8 01 00 00 6b c1 0c 8b 75 18 8b 7d 1c 8b 54 03
20 01 72 74 11 7a 78 8b 45 b4 89 4d a4 e8 6d fe ff ff 8b 4d a4 85 c0 74 04
<0f> 0b eb fe 41 3b 4b 18 7c d1 8b 45 cc 89 da 31 c9 83 c0 30 eb
> [ 519.625868] EIP: [<c11450e7>] __finish_chunk_alloc+0x77/0x202
SS:ESP 0068:dc995bf8
> [ 519.625881] ---[ end trace b163863f8b1f1b85 ]---
>
Thank you for reporting it. I can reproduce the bug.
Yan, Zheng
--
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