* hitting BUG_ON on troublesome FS
@ 2014-02-03 20:51 Remco Hosman - Yerf-it.com
2014-02-04 6:21 ` Duncan
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Remco Hosman - Yerf-it.com @ 2014-02-03 20:51 UTC (permalink / raw)
To: linux-btrfs; +Cc: zheng.yan
FIrst, a bit of history of the filesystem:
used to be 6 disks, now 5. partially raid1 / raid10. been migrating back and forth a few times.
As some point, a balance would not complete and would end with 164 ENOSPC’ses, while there was plenty of unallocated space on each disk.
i scanned for extends larger then 1gig and found a few, so ran a recursive balance of the entire FS.
I deceided to empty the filesystem and format it.
i pulled most files off it some via btrfs send/receive, some via rsync. but 1 subvol wouldn’t send. i don’t remember the exact error, but it was that a extend could not be found on 1 of the disks.
with only a few 100gig of data left, i decided to balance some remaining empty space before doing a `btrfs dev del`, so have another disk to store more data on.
but im hitting a snag, i hit a BUG_ON when doing a `btrfs bal start -dusage=2 /mountpoint` :
[ 3327.678329] btrfs: found 198 extents
[ 3328.117274] btrfs: relocating block group 84473084968960 flags 17
[ 3329.278521] btrfs: found 103 extents
[ 3331.907931] btrfs: found 103 extents
[ 3332.386172] btrfs: relocating block group 84466642518016 flags 17
[ 3333.536595] btrfs: found 86 extents
[ 3335.982967] btrfs: found 86 extents
[ 3336.599555] btrfs (4746) used greatest stack depth: 2744 bytes left
[ 3379.073464] btrfs: relocating block group 89878368419840 flags 17
[ 3381.608948] btrfs: found 499 extents
[ 3383.884696] ------------[ cut here ]------------
[ 3383.884720] kernel BUG at fs/btrfs/relocation.c:3405!
[ 3383.884731] invalid opcode: 0000 [#1] SMP
[ 3383.884742] Modules linked in:
[ 3383.884753] CPU: 0 PID: 5663 Comm: btrfs Not tainted 3.13.0 #1
[ 3383.884763] Hardware name: System manufacturer System Product Name/E45M1-I DELUXE, BIOS 0405 08/08/2012
[ 3383.884778] task: ffff8802360eae80 ti: ffff88010dcaa000 task.ti: ffff88010dcaa000
[ 3383.884790] RIP: 0010:[<ffffffff812f0bd5>] [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
[ 3383.884811] RSP: 0018:ffff88010dcaba38 EFLAGS: 00010202
[ 3383.884821] RAX: 0000000000000001 RBX: ffff880039f18000 RCX: 00000000ffffffff
[ 3383.884832] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 3383.884843] RBP: ffff88010dcaba90 R08: ffff88010dcab9f4 R09: ffff88010dcab930
[ 3383.884854] R10: 0000000000000000 R11: 000000000000047f R12: 0000000000001000
[ 3383.884865] R13: ffff88023489c630 R14: 0000000000000000 R15: 0000528d112e4000
[ 3383.884876] FS: 00007f8e27e74880(0000) GS:ffff88023ec00000(0000) knlGS:0000000000000000
[ 3383.884888] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 3383.884897] CR2: 00007f60d89f35a8 CR3: 00000001b5ada000 CR4: 00000000000007f0
[ 3383.884907] Stack:
[ 3383.884941] ffff88010dcabb28 4000ffff812bde34 00a80000528d112e 0000000000000010
[ 3383.885012] 0000000000001000 0000000000001000 0000000000000f3a ffff8802348d6990
[ 3383.885082] ffff88001cbf5a00 ffff880039f18000 00000000000000b8 ffff88010dcabb00
[ 3383.885153] Call Trace:
[ 3383.885192] [<ffffffff812f1a54>] add_data_references+0x244/0x2e0
[ 3383.885232] [<ffffffff812f2a2b>] relocate_block_group+0x56b/0x640
[ 3383.885272] [<ffffffff812f2ca2>] btrfs_relocate_block_group+0x1a2/0x2f0
[ 3383.885313] [<ffffffff812cbcca>] btrfs_relocate_chunk.isra.27+0x6a/0x740
[ 3383.885355] [<ffffffff81281a31>] ? btrfs_set_path_blocking+0x31/0x70
[ 3383.885432] [<ffffffff81286816>] ? btrfs_search_slot+0x386/0x960
[ 3383.885473] [<ffffffff812c6f07>] ? free_extent_buffer+0x47/0xa0
[ 3383.885513] [<ffffffff812ceedb>] btrfs_balance+0x90b/0xea0
[ 3383.885553] [<ffffffff812d5ec2>] btrfs_ioctl_balance+0x162/0x520
[ 3383.885592] [<ffffffff812d9aed>] btrfs_ioctl+0xcbd/0x25c0
[ 3383.885632] [<ffffffff818c094c>] ? __do_page_fault+0x1dc/0x520
[ 3383.885673] [<ffffffff81136868>] do_vfs_ioctl+0x2c8/0x490
[ 3383.885712] [<ffffffff81136ab1>] SyS_ioctl+0x81/0xa0
[ 3383.885752] [<ffffffff818c4f5b>] tracesys+0xdd/0xe2
[ 3383.885787] Code: ff 48 8b 4d a8 48 8d 75 b6 4c 89 ea 48 89 df e8 42 e7 ff ff 4c 89 ef 89 45 a8 e8 c7 0f f9 ff 8b 45 a8 e9 69 ff ff ff 85 c0 74 d6 <0f> 0b 66 0f 1f 84 00 00 00 00 00 b8 f4 ff ff ff e9 50 ff ff ff
[ 3383.886001] RIP [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
[ 3383.886042] RSP <ffff88010dcaba38>
[ 3383.886359] ---[ end trace 075209044ce10da3 ]---
Anything i can do to resolve / debug the issue?
Remco
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: hitting BUG_ON on troublesome FS
2014-02-03 20:51 hitting BUG_ON on troublesome FS Remco Hosman - Yerf-it.com
@ 2014-02-04 6:21 ` Duncan
2014-02-04 19:12 ` Remco Hosman - Yerf-it.com
2014-02-04 21:48 ` Josef Bacik
2 siblings, 0 replies; 6+ messages in thread
From: Duncan @ 2014-02-04 6:21 UTC (permalink / raw)
To: linux-btrfs
Remco Hosman - Yerf-it.com posted on Mon, 03 Feb 2014 21:51:26 +0100 as
excerpted:
> Anything i can do to resolve / debug the issue?
I see from the trace you're running kernel 3.13.0. (FWIW 3.13.1 is out,
but there weren't any btrfs commits therein, as they weren't upstream in
3.14-pre yet at that time.)
You might try kernel 3.14-rc1 now that it's out. There's a big btrfs git
pull in that, including a number of btrfs send/receive fixes. FWIW,
btrfs send/receive seems to be a big focus right now, and I see a lot of
patches floating by on the list even after that pull, so there's more
where those came from.
I'm not a dev (just another btrfs user and list regular for several
kernel cycles now) and haven't followed the patches closely enough to
know if your particular balance problem is covered in one of them, but as
I said, since 3.14-rc1 is out now, you might as well try it...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: hitting BUG_ON on troublesome FS
2014-02-03 20:51 hitting BUG_ON on troublesome FS Remco Hosman - Yerf-it.com
2014-02-04 6:21 ` Duncan
@ 2014-02-04 19:12 ` Remco Hosman - Yerf-it.com
2014-02-04 21:48 ` Josef Bacik
2 siblings, 0 replies; 6+ messages in thread
From: Remco Hosman - Yerf-it.com @ 2014-02-04 19:12 UTC (permalink / raw)
To: linux-btrfs
to reply to my own thread:
i managed to empty the filesystem, but it still segfaults in the same way when i try to balance the last few blocks. a `btrfs bal start -dusage=0 /mountpoint` finishes, but leaves a few blocks allocated. when i skip the usage=0, it segfaults.
What can i do to provide useful information?
Remco
On 03 Feb 2014, at 21:51, Remco Hosman - Yerf-it.com <remco@yerf-it.com> wrote:
> FIrst, a bit of history of the filesystem:
> used to be 6 disks, now 5. partially raid1 / raid10. been migrating back and forth a few times.
> As some point, a balance would not complete and would end with 164 ENOSPC’ses, while there was plenty of unallocated space on each disk.
>
> i scanned for extends larger then 1gig and found a few, so ran a recursive balance of the entire FS.
>
> I deceided to empty the filesystem and format it.
>
> i pulled most files off it some via btrfs send/receive, some via rsync. but 1 subvol wouldn’t send. i don’t remember the exact error, but it was that a extend could not be found on 1 of the disks.
>
> with only a few 100gig of data left, i decided to balance some remaining empty space before doing a `btrfs dev del`, so have another disk to store more data on.
> but im hitting a snag, i hit a BUG_ON when doing a `btrfs bal start -dusage=2 /mountpoint` :
>
> [ 3327.678329] btrfs: found 198 extents
> [ 3328.117274] btrfs: relocating block group 84473084968960 flags 17
> [ 3329.278521] btrfs: found 103 extents
> [ 3331.907931] btrfs: found 103 extents
> [ 3332.386172] btrfs: relocating block group 84466642518016 flags 17
> [ 3333.536595] btrfs: found 86 extents
> [ 3335.982967] btrfs: found 86 extents
> [ 3336.599555] btrfs (4746) used greatest stack depth: 2744 bytes left
> [ 3379.073464] btrfs: relocating block group 89878368419840 flags 17
> [ 3381.608948] btrfs: found 499 extents
> [ 3383.884696] ------------[ cut here ]------------
> [ 3383.884720] kernel BUG at fs/btrfs/relocation.c:3405!
> [ 3383.884731] invalid opcode: 0000 [#1] SMP
> [ 3383.884742] Modules linked in:
> [ 3383.884753] CPU: 0 PID: 5663 Comm: btrfs Not tainted 3.13.0 #1
> [ 3383.884763] Hardware name: System manufacturer System Product Name/E45M1-I DELUXE, BIOS 0405 08/08/2012
> [ 3383.884778] task: ffff8802360eae80 ti: ffff88010dcaa000 task.ti: ffff88010dcaa000
> [ 3383.884790] RIP: 0010:[<ffffffff812f0bd5>] [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
> [ 3383.884811] RSP: 0018:ffff88010dcaba38 EFLAGS: 00010202
> [ 3383.884821] RAX: 0000000000000001 RBX: ffff880039f18000 RCX: 00000000ffffffff
> [ 3383.884832] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> [ 3383.884843] RBP: ffff88010dcaba90 R08: ffff88010dcab9f4 R09: ffff88010dcab930
> [ 3383.884854] R10: 0000000000000000 R11: 000000000000047f R12: 0000000000001000
> [ 3383.884865] R13: ffff88023489c630 R14: 0000000000000000 R15: 0000528d112e4000
> [ 3383.884876] FS: 00007f8e27e74880(0000) GS:ffff88023ec00000(0000) knlGS:0000000000000000
> [ 3383.884888] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 3383.884897] CR2: 00007f60d89f35a8 CR3: 00000001b5ada000 CR4: 00000000000007f0
> [ 3383.884907] Stack:
> [ 3383.884941] ffff88010dcabb28 4000ffff812bde34 00a80000528d112e 0000000000000010
> [ 3383.885012] 0000000000001000 0000000000001000 0000000000000f3a ffff8802348d6990
> [ 3383.885082] ffff88001cbf5a00 ffff880039f18000 00000000000000b8 ffff88010dcabb00
> [ 3383.885153] Call Trace:
> [ 3383.885192] [<ffffffff812f1a54>] add_data_references+0x244/0x2e0
> [ 3383.885232] [<ffffffff812f2a2b>] relocate_block_group+0x56b/0x640
> [ 3383.885272] [<ffffffff812f2ca2>] btrfs_relocate_block_group+0x1a2/0x2f0
> [ 3383.885313] [<ffffffff812cbcca>] btrfs_relocate_chunk.isra.27+0x6a/0x740
> [ 3383.885355] [<ffffffff81281a31>] ? btrfs_set_path_blocking+0x31/0x70
> [ 3383.885432] [<ffffffff81286816>] ? btrfs_search_slot+0x386/0x960
> [ 3383.885473] [<ffffffff812c6f07>] ? free_extent_buffer+0x47/0xa0
> [ 3383.885513] [<ffffffff812ceedb>] btrfs_balance+0x90b/0xea0
> [ 3383.885553] [<ffffffff812d5ec2>] btrfs_ioctl_balance+0x162/0x520
> [ 3383.885592] [<ffffffff812d9aed>] btrfs_ioctl+0xcbd/0x25c0
> [ 3383.885632] [<ffffffff818c094c>] ? __do_page_fault+0x1dc/0x520
> [ 3383.885673] [<ffffffff81136868>] do_vfs_ioctl+0x2c8/0x490
> [ 3383.885712] [<ffffffff81136ab1>] SyS_ioctl+0x81/0xa0
> [ 3383.885752] [<ffffffff818c4f5b>] tracesys+0xdd/0xe2
> [ 3383.885787] Code: ff 48 8b 4d a8 48 8d 75 b6 4c 89 ea 48 89 df e8 42 e7 ff ff 4c 89 ef 89 45 a8 e8 c7 0f f9 ff 8b 45 a8 e9 69 ff ff ff 85 c0 74 d6 <0f> 0b 66 0f 1f 84 00 00 00 00 00 b8 f4 ff ff ff e9 50 ff ff ff
> [ 3383.886001] RIP [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
> [ 3383.886042] RSP <ffff88010dcaba38>
> [ 3383.886359] ---[ end trace 075209044ce10da3 ]---
> Anything i can do to resolve / debug the issue?
>
> Remco--
> 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] 6+ messages in thread
* Re: hitting BUG_ON on troublesome FS
2014-02-03 20:51 hitting BUG_ON on troublesome FS Remco Hosman - Yerf-it.com
2014-02-04 6:21 ` Duncan
2014-02-04 19:12 ` Remco Hosman - Yerf-it.com
@ 2014-02-04 21:48 ` Josef Bacik
2014-02-05 6:35 ` Remco Hosman - Yerf-it.com
[not found] ` <50C9BA7F-4988-4765-963C-20B241A13C84@yerf-it.com>
2 siblings, 2 replies; 6+ messages in thread
From: Josef Bacik @ 2014-02-04 21:48 UTC (permalink / raw)
To: Remco Hosman - Yerf-it.com, linux-btrfs; +Cc: zheng.yan
On 02/03/2014 03:51 PM, Remco Hosman - Yerf-it.com wrote:
> FIrst, a bit of history of the filesystem:
> used to be 6 disks, now 5. partially raid1 / raid10. been migrating back and forth a few times.
> As some point, a balance would not complete and would end with 164 ENOSPC’ses, while there was plenty of unallocated space on each disk.
>
> i scanned for extends larger then 1gig and found a few, so ran a recursive balance of the entire FS.
>
> I deceided to empty the filesystem and format it.
>
> i pulled most files off it some via btrfs send/receive, some via rsync. but 1 subvol wouldn’t send. i don’t remember the exact error, but it was that a extend could not be found on 1 of the disks.
>
> with only a few 100gig of data left, i decided to balance some remaining empty space before doing a `btrfs dev del`, so have another disk to store more data on.
> but im hitting a snag, i hit a BUG_ON when doing a `btrfs bal start -dusage=2 /mountpoint` :
>
> [ 3327.678329] btrfs: found 198 extents
> [ 3328.117274] btrfs: relocating block group 84473084968960 flags 17
> [ 3329.278521] btrfs: found 103 extents
> [ 3331.907931] btrfs: found 103 extents
> [ 3332.386172] btrfs: relocating block group 84466642518016 flags 17
> [ 3333.536595] btrfs: found 86 extents
> [ 3335.982967] btrfs: found 86 extents
> [ 3336.599555] btrfs (4746) used greatest stack depth: 2744 bytes left
> [ 3379.073464] btrfs: relocating block group 89878368419840 flags 17
> [ 3381.608948] btrfs: found 499 extents
> [ 3383.884696] ------------[ cut here ]------------
> [ 3383.884720] kernel BUG at fs/btrfs/relocation.c:3405!
> [ 3383.884731] invalid opcode: 0000 [#1] SMP
> [ 3383.884742] Modules linked in:
> [ 3383.884753] CPU: 0 PID: 5663 Comm: btrfs Not tainted 3.13.0 #1
> [ 3383.884763] Hardware name: System manufacturer System Product Name/E45M1-I DELUXE, BIOS 0405 08/08/2012
> [ 3383.884778] task: ffff8802360eae80 ti: ffff88010dcaa000 task.ti: ffff88010dcaa000
> [ 3383.884790] RIP: 0010:[<ffffffff812f0bd5>] [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
> [ 3383.884811] RSP: 0018:ffff88010dcaba38 EFLAGS: 00010202
> [ 3383.884821] RAX: 0000000000000001 RBX: ffff880039f18000 RCX: 00000000ffffffff
> [ 3383.884832] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> [ 3383.884843] RBP: ffff88010dcaba90 R08: ffff88010dcab9f4 R09: ffff88010dcab930
> [ 3383.884854] R10: 0000000000000000 R11: 000000000000047f R12: 0000000000001000
> [ 3383.884865] R13: ffff88023489c630 R14: 0000000000000000 R15: 0000528d112e4000
> [ 3383.884876] FS: 00007f8e27e74880(0000) GS:ffff88023ec00000(0000) knlGS:0000000000000000
> [ 3383.884888] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> [ 3383.884897] CR2: 00007f60d89f35a8 CR3: 00000001b5ada000 CR4: 00000000000007f0
> [ 3383.884907] Stack:
> [ 3383.884941] ffff88010dcabb28 4000ffff812bde34 00a80000528d112e 0000000000000010
> [ 3383.885012] 0000000000001000 0000000000001000 0000000000000f3a ffff8802348d6990
> [ 3383.885082] ffff88001cbf5a00 ffff880039f18000 00000000000000b8 ffff88010dcabb00
> [ 3383.885153] Call Trace:
> [ 3383.885192] [<ffffffff812f1a54>] add_data_references+0x244/0x2e0
> [ 3383.885232] [<ffffffff812f2a2b>] relocate_block_group+0x56b/0x640
> [ 3383.885272] [<ffffffff812f2ca2>] btrfs_relocate_block_group+0x1a2/0x2f0
> [ 3383.885313] [<ffffffff812cbcca>] btrfs_relocate_chunk.isra.27+0x6a/0x740
> [ 3383.885355] [<ffffffff81281a31>] ? btrfs_set_path_blocking+0x31/0x70
> [ 3383.885432] [<ffffffff81286816>] ? btrfs_search_slot+0x386/0x960
> [ 3383.885473] [<ffffffff812c6f07>] ? free_extent_buffer+0x47/0xa0
> [ 3383.885513] [<ffffffff812ceedb>] btrfs_balance+0x90b/0xea0
> [ 3383.885553] [<ffffffff812d5ec2>] btrfs_ioctl_balance+0x162/0x520
> [ 3383.885592] [<ffffffff812d9aed>] btrfs_ioctl+0xcbd/0x25c0
> [ 3383.885632] [<ffffffff818c094c>] ? __do_page_fault+0x1dc/0x520
> [ 3383.885673] [<ffffffff81136868>] do_vfs_ioctl+0x2c8/0x490
> [ 3383.885712] [<ffffffff81136ab1>] SyS_ioctl+0x81/0xa0
> [ 3383.885752] [<ffffffff818c4f5b>] tracesys+0xdd/0xe2
> [ 3383.885787] Code: ff 48 8b 4d a8 48 8d 75 b6 4c 89 ea 48 89 df e8 42 e7 ff ff 4c 89 ef 89 45 a8 e8 c7 0f f9 ff 8b 45 a8 e9 69 ff ff ff 85 c0 74 d6 <0f> 0b 66 0f 1f 84 00 00 00 00 00 b8 f4 ff ff ff e9 50 ff ff ff
> [ 3383.886001] RIP [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
> [ 3383.886042] RSP <ffff88010dcaba38>
> [ 3383.886359] ---[ end trace 075209044ce10da3 ]---
> Anything i can do to resolve / debug the issue?
>
Are you using skinny extents at all? Thanks,
Josef
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: hitting BUG_ON on troublesome FS
2014-02-04 21:48 ` Josef Bacik
@ 2014-02-05 6:35 ` Remco Hosman - Yerf-it.com
[not found] ` <50C9BA7F-4988-4765-963C-20B241A13C84@yerf-it.com>
1 sibling, 0 replies; 6+ messages in thread
From: Remco Hosman - Yerf-it.com @ 2014-02-05 6:35 UTC (permalink / raw)
To: linux-btrfs
How can i tell?
Label: data uuid: a8626d67-4684-4b23-99b3-8d5fa8e7fd69
Total devices 5 FS bytes used 820.00KiB
devid 2 size 1.82TiB used 1.00GiB path /dev/sdb2
devid 3 size 1.82TiB used 1.00GiB path /dev/sdf2
devid 5 size 2.73TiB used 3.00GiB path /dev/sdd2
devid 10 size 2.73TiB used 2.03GiB path /dev/sde2
devid 11 size 3.64TiB used 1.03GiB path /dev/sdc1
Data, RAID10: total=3D2.00GiB, used=3D768.00KiB
Data, RAID1: total=3D1.00GiB, used=3D12.00KiB
System, RAID1: total=3D32.00MiB, used=3D4.00KiB
Metadata, RAID1: total=3D1.00GiB, used=3D36.00KiB
i made a image with `btrfs-image`, when i do -c 9, the file size is 7k, =
so eazy enough to mail if it would be of any use.
Remco
On 04 Feb 2014, at 22:48, Josef Bacik <jbacik@fb.com> wrote:
>
> On 02/03/2014 03:51 PM, Remco Hosman - Yerf-it.com wrote:
>> FIrst, a bit of history of the filesystem:
>> used to be 6 disks, now 5. partially raid1 / raid10. been migrating back and forth a few times.
>> As some point, a balance would not complete and would end with 164 ENOSPC’ses, while there was plenty of unallocated space on each disk.
>>
>> i scanned for extends larger then 1gig and found a few, so ran a recursive balance of the entire FS.
>>
>> I deceided to empty the filesystem and format it.
>>
>> i pulled most files off it some via btrfs send/receive, some via rsync. but 1 subvol wouldn’t send. i don’t remember the exact error, but it was that a extend could not be found on 1 of the disks.
>>
>> with only a few 100gig of data left, i decided to balance some remaining empty space before doing a `btrfs dev del`, so have another disk to store more data on.
>> but im hitting a snag, i hit a BUG_ON when doing a `btrfs bal start -dusage=2 /mountpoint` :
>>
>> [ 3327.678329] btrfs: found 198 extents
>> [ 3328.117274] btrfs: relocating block group 84473084968960 flags 17
>> [ 3329.278521] btrfs: found 103 extents
>> [ 3331.907931] btrfs: found 103 extents
>> [ 3332.386172] btrfs: relocating block group 84466642518016 flags 17
>> [ 3333.536595] btrfs: found 86 extents
>> [ 3335.982967] btrfs: found 86 extents
>> [ 3336.599555] btrfs (4746) used greatest stack depth: 2744 bytes left
>> [ 3379.073464] btrfs: relocating block group 89878368419840 flags 17
>> [ 3381.608948] btrfs: found 499 extents
>> [ 3383.884696] ------------[ cut here ]------------
>> [ 3383.884720] kernel BUG at fs/btrfs/relocation.c:3405!
>> [ 3383.884731] invalid opcode: 0000 [#1] SMP
>> [ 3383.884742] Modules linked in:
>> [ 3383.884753] CPU: 0 PID: 5663 Comm: btrfs Not tainted 3.13.0 #1
>> [ 3383.884763] Hardware name: System manufacturer System Product Name/E45M1-I DELUXE, BIOS 0405 08/08/2012
>> [ 3383.884778] task: ffff8802360eae80 ti: ffff88010dcaa000 task.ti: ffff88010dcaa000
>> [ 3383.884790] RIP: 0010:[<ffffffff812f0bd5>] [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
>> [ 3383.884811] RSP: 0018:ffff88010dcaba38 EFLAGS: 00010202
>> [ 3383.884821] RAX: 0000000000000001 RBX: ffff880039f18000 RCX: 00000000ffffffff
>> [ 3383.884832] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
>> [ 3383.884843] RBP: ffff88010dcaba90 R08: ffff88010dcab9f4 R09: ffff88010dcab930
>> [ 3383.884854] R10: 0000000000000000 R11: 000000000000047f R12: 0000000000001000
>> [ 3383.884865] R13: ffff88023489c630 R14: 0000000000000000 R15: 0000528d112e4000
>> [ 3383.884876] FS: 00007f8e27e74880(0000) GS:ffff88023ec00000(0000) knlGS:0000000000000000
>> [ 3383.884888] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>> [ 3383.884897] CR2: 00007f60d89f35a8 CR3: 00000001b5ada000 CR4: 00000000000007f0
>> [ 3383.884907] Stack:
>> [ 3383.884941] ffff88010dcabb28 4000ffff812bde34 00a80000528d112e 0000000000000010
>> [ 3383.885012] 0000000000001000 0000000000001000 0000000000000f3a ffff8802348d6990
>> [ 3383.885082] ffff88001cbf5a00 ffff880039f18000 00000000000000b8 ffff88010dcabb00
>> [ 3383.885153] Call Trace:
>> [ 3383.885192] [<ffffffff812f1a54>] add_data_references+0x244/0x2e0
>> [ 3383.885232] [<ffffffff812f2a2b>] relocate_block_group+0x56b/0x640
>> [ 3383.885272] [<ffffffff812f2ca2>] btrfs_relocate_block_group+0x1a2/0x2f0
>> [ 3383.885313] [<ffffffff812cbcca>] btrfs_relocate_chunk.isra.27+0x6a/0x740
>> [ 3383.885355] [<ffffffff81281a31>] ? btrfs_set_path_blocking+0x31/0x70
>> [ 3383.885432] [<ffffffff81286816>] ? btrfs_search_slot+0x386/0x960
>> [ 3383.885473] [<ffffffff812c6f07>] ? free_extent_buffer+0x47/0xa0
>> [ 3383.885513] [<ffffffff812ceedb>] btrfs_balance+0x90b/0xea0
>> [ 3383.885553] [<ffffffff812d5ec2>] btrfs_ioctl_balance+0x162/0x520
>> [ 3383.885592] [<ffffffff812d9aed>] btrfs_ioctl+0xcbd/0x25c0
>> [ 3383.885632] [<ffffffff818c094c>] ? __do_page_fault+0x1dc/0x520
>> [ 3383.885673] [<ffffffff81136868>] do_vfs_ioctl+0x2c8/0x490
>> [ 3383.885712] [<ffffffff81136ab1>] SyS_ioctl+0x81/0xa0
>> [ 3383.885752] [<ffffffff818c4f5b>] tracesys+0xdd/0xe2
>> [ 3383.885787] Code: ff 48 8b 4d a8 48 8d 75 b6 4c 89 ea 48 89 df e8 42 e7 ff ff 4c 89 ef 89 45 a8 e8 c7 0f f9 ff 8b 45 a8 e9 69 ff ff ff 85 c0 74 d6 <0f> 0b 66 0f 1f 84 00 00 00 00 00 b8 f4 ff ff ff e9 50 ff ff ff
>> [ 3383.886001] RIP [<ffffffff812f0bd5>] __add_tree_block+0x1c5/0x1e0
>> [ 3383.886042] RSP <ffff88010dcaba38>
>> [ 3383.886359] ---[ end trace 075209044ce10da3 ]---
>> Anything i can do to resolve / debug the issue?
>>
> Are you using skinny extents at all? Thanks,
>
> Josef
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: hitting BUG_ON on troublesome FS
[not found] ` <50C9BA7F-4988-4765-963C-20B241A13C84@yerf-it.com>
@ 2014-02-05 14:22 ` Josef Bacik
0 siblings, 0 replies; 6+ messages in thread
From: Josef Bacik @ 2014-02-05 14:22 UTC (permalink / raw)
To: Remco Hosman - Yerf-it.com; +Cc: linux-btrfs
On 02/05/2014 01:34 AM, Remco Hosman - Yerf-it.com wrote:
> How can i tell?
>
> Label: data uuid: a8626d67-4684-4b23-99b3-8d5fa8e7fd69
> Total devices 5 FS bytes used 820.00KiB
> devid 2 size 1.82TiB used 1.00GiB path /dev/sdb2
> devid 3 size 1.82TiB used 1.00GiB path /dev/sdf2
> devid 5 size 2.73TiB used 3.00GiB path /dev/sdd2
> devid 10 size 2.73TiB used 2.03GiB path /dev/sde2
> devid 11 size 3.64TiB used 1.03GiB path /dev/sdc1
>
> Data, RAID10: total=2.00GiB, used=768.00KiB
> Data, RAID1: total=1.00GiB, used=12.00KiB
> System, RAID1: total=32.00MiB, used=4.00KiB
> Metadata, RAID1: total=1.00GiB, used=36.00KiB
>
> i made a image with `btrfs-image`, when i do -c 9, the file size is
> 7k, so eazy enough to mail if it would be of any use.
>
Yup that would be perfect. THanks,
Josef
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-02-05 14:22 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-03 20:51 hitting BUG_ON on troublesome FS Remco Hosman - Yerf-it.com
2014-02-04 6:21 ` Duncan
2014-02-04 19:12 ` Remco Hosman - Yerf-it.com
2014-02-04 21:48 ` Josef Bacik
2014-02-05 6:35 ` Remco Hosman - Yerf-it.com
[not found] ` <50C9BA7F-4988-4765-963C-20B241A13C84@yerf-it.com>
2014-02-05 14:22 ` Josef Bacik
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.