btrfs bug

btrfs bug

[Thomas Weber]

Hello,

this morning my laptop with btrfs crashed. It is an ssd drive.

It is a Linux aramis 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:40:20 CET 
2012 x86_64 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel 
GNU/Linux

Regards,
Thomas


This two lines are from a photo, that i made.
 > kernel BUG at fs/btrfs/extent_io.c:4357!
 > invalid opcode: 0000 [#1] PREEMPT SMP

The rest is from dmesg.

Jan 31 05:12:24 localhost kernel: [87276.968388] CPU 1
Jan 31 05:12:24 localhost kernel: [87276.968423] Modules linked in: nfs 
nfs_acl lockd auth_rpcgss sunrpc des_generic ecb md4 md5 hmac nls_utf8 
cifs fscache aes_generic ipv6 ext2 mbcache joydev arc4 dell_wmi 
sparse_keymap i915 snd_hda_codec_idt iwl3945 iwl_legacy psmouse 
snd_hda_intel serio_raw evdev pcspkr snd_hda_codec drm_kms_helper 
snd_hwdep mac80211 snd_pcm snd_page_alloc snd_timer drm cfg80211 
i2c_algo_bit i2c_i801 tg3 snd iTCO_wdt iTCO_vendor_support soundcore 
rfkill i2c_core libphy wmi intel_agp intel_gtt thermal button battery 
video processor ac btrfs crc32c libcrc32c zlib_deflate sd_mod pata_acpi 
uhci_hcd ata_piix libata scsi_mod ehci_hcd usbcore usb_common
Jan 31 05:12:24 localhost kernel: [87276.969644]
Jan 31 05:12:24 localhost kernel: [87276.969674] Pid: 15299, comm: 
btrfs-endio-wri Not tainted 3.2.2-1-ARCH #1 Dell Inc. Latitude 
D530                   /0HP728
Jan 31 05:12:24 localhost kernel: [87276.969831] RIP: 
0010:[<ffffffffa01d535a>]  [<ffffffffa01d535a>] 
memmove_extent_buffer+0x30a/0x310 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.969995] RSP: 
0018:ffff880057ceba90  EFLAGS: 00010282
Jan 31 05:12:24 localhost kernel: [87276.970065] RAX: 0000000000000055 
RBX: 00000000290029b3 RCX: 00000000000000f6
Jan 31 05:12:24 localhost kernel: [87276.970153] RDX: 0000000000000000 
RSI: 0000000000000046 RDI: 0000000000000202
Jan 31 05:12:24 localhost kernel: [87276.970240] RBP: ffff880057cebb00 
R08: 000000000000000a R09: 0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.970330] R10: 0000000000000000 
R11: 0000000000000001 R12: ffff88010e9d9b40
Jan 31 05:12:24 localhost kernel: [87276.970419] R13: 00000000000006e9 
R14: 0000000029003101 R15: 000000000000002a
Jan 31 05:12:24 localhost kernel: [87276.970507] FS:  
0000000000000000(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.970610] CS:  0010 DS: 0000 ES: 
0000 CR0: 000000008005003b
Jan 31 05:12:24 localhost kernel: [87276.970681] CR2: 0000000001c63018 
CR3: 000000005ad52000 CR4: 00000000000006e0
Jan 31 05:12:24 localhost kernel: [87276.970769] DR0: 0000000000000000 
DR1: 0000000000000000 DR2: 0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.970856] DR3: 0000000000000000 
DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 31 05:12:24 localhost kernel: [87276.970945] Process btrfs-endio-wri 
(pid: 15299, threadinfo ffff880057cea000, task ffff880103cb1c80)
Jan 31 05:12:24 localhost kernel: [87276.971087]  0000000000000466 
00000000000006b4 0000000000000477 ffff88010e9d9b40
Jan 31 05:12:24 localhost kernel: [87276.971206]  ffff88010e9d9b40 
0000000000000000 0000160000000000 0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.971286]  0000000000001000 
ffff880057cebc7c ffff88010e9d9b40 00000000000006e9
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa0198251>] 
setup_items_for_insert+0x181/0x350 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01985e5>] 
btrfs_insert_empty_items+0xb5/0xe0 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01b8940>] 
insert_reserved_file_extent.constprop.52+0xc0/0x270 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01b98fa>] 
btrfs_finish_ordered_io+0x2ca/0x320 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01b999d>] 
btrfs_writepage_end_io_hook+0x4d/0xf0 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01cf03f>] 
end_bio_extent_writepage+0x12f/0x170 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff8119ba0d>] 
bio_endio+0x1d/0x40
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01ac736>] 
end_workqueue_fn+0x56/0x140 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01dc920>] 
worker_loop+0x150/0x520 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01dc7d0>] ? 
btrfs_queue_worker+0x300/0x300 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff810883fc>] 
kthread+0x8c/0xa0
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff8142b874>] 
kernel_thread_helper+0x4/0x10
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff81088370>] ? 
kthread_worker_fn+0x190/0x190
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff8142b870>] ? 
gs_change+0x13/0x13
Jan 31 05:12:24 localhost kernel: [87276.971286]  RSP <ffff880057ceba90>
Jan 31 05:12:24 localhost kernel: [87276.993478] ---[ end trace 
174f2acd3ea6a532 ]---
Jan 31 05:12:24 localhost kernel: [87276.993491] note: 
btrfs-endio-wri[15299] exited with preempt_count 1
Jan 31 05:32:24 localhost -- MARK --

Re: btrfs bug

[Mitch Harder]

On Tue, Jan 31, 2012 at 12:04 PM, Thomas Weber
<thomas.weber.linux@googlemail.com> wrote:
> Hello,
>
> this morning my laptop with btrfs crashed. It is an ssd drive.
>
> It is a Linux aramis 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:40:20 CET
> 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel
> GNU/Linux
>
> Regards,
> Thomas
>
>
> This two lines are from a photo, that i made.
>> kernel BUG at fs/btrfs/extent_io.c:4357!
>> invalid opcode: 0000 [#1] PREEMPT SMP
>
> The rest is from dmesg.
>

In your dmesg output, immediately prior to what you posted, there
should have been a message like: "btrfs memmove bogus src_offset %lu
move len %lu len %lu".

If you still have this output, could you post that line with its values?

Re: btrfs bug

[Thomas Weber]

Hello Mitch,

On 01/31/2012 10:37 PM, Mitch Harder wrote:
> On Tue, Jan 31, 2012 at 12:04 PM, Thomas Weber
> <thomas.weber.linux@googlemail.com>  wrote:
>> Hello,
>>
>> this morning my laptop with btrfs crashed. It is an ssd drive.
>>
>> It is a Linux aramis 3.2.2-1-ARCH #1 SMP PREEMPT Thu Jan 26 08:40:20 CET
>> 2012 x86_64 Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz GenuineIntel
>> GNU/Linux
>>
>> Regards,
>> Thomas
>>
>>
>> This two lines are from a photo, that i made.
>>> kernel BUG at fs/btrfs/extent_io.c:4357!
>>> invalid opcode: 0000 [#1] PREEMPT SMP
>> The rest is from dmesg.
>>
> In your dmesg output, immediately prior to what you posted, there
> should have been a message like: "btrfs memmove bogus src_offset %lu
> move len %lu len %lu".
>
> If you still have this output, could you post that line with its values?
no, sorry i don't have more output.

Thomas

Re: btrfs bug

[Thomas Weber]

Hello Mitch,

I have good news for you. I looked through all log files and found in 
the everything.log the following:

Regards,
Thomas


Jan 31 05:12:24 localhost kernel: [87276.968049] btrfs memmove bogus 
src_offset 1870 move len 687876531 len 4096
Jan 31 05:12:24 localhost kernel: [87276.968136] ------------[ cut here 
]------------
Jan 31 05:12:24 localhost kernel: [87276.968222] kernel BUG at 
fs/btrfs/extent_io.c:4357!
Jan 31 05:12:24 localhost kernel: [87276.968296] invalid opcode: 0000 
[#1] PREEMPT SMP
Jan 31 05:12:24 localhost kernel: [87276.968388] CPU 1
Jan 31 05:12:24 localhost kernel: [87276.968423] Modules linked in: nfs 
nfs_acl lockd auth_rpcgss sunrpc des_generic ecb md4 md5 hmac nls_utf8 
cifs fscache aes_generic ipv6 ext2 mbcache joydev arc4 dell_wmi 
sparse_keymap i915 snd_hda_codec_idt iwl3945 iwl_legacy psmouse 
snd_hda_intel serio_raw evdev pcspkr snd_hda_codec drm_kms_helper 
snd_hwdep mac80211 snd_pcm snd_page_alloc snd_timer drm cfg80211 
i2c_algo_bit i2c_i801 tg3 snd iTCO_wdt iTCO_vendor_support soundcore 
rfkill i2c_core libphy wmi intel_agp intel_gtt thermal button battery 
video processor ac btrfs crc32c libcrc32c zlib_deflate sd_mod pata_acpi 
uhci_hcd ata_piix libata scsi_mod ehci_hcd usbcore usb_common
Jan 31 05:12:24 localhost kernel: [87276.969644]
Jan 31 05:12:24 localhost kernel: [87276.969674] Pid: 15299, comm: 
btrfs-endio-wri Not tainted 3.2.2-1-ARCH #1 Dell Inc. Latitude 
D530                   /0HP728
Jan 31 05:12:24 localhost kernel: [87276.969831] RIP: 
0010:[<ffffffffa01d535a>]  [<ffffffffa01d535a>] 
memmove_extent_buffer+0x30a/0x310 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.969995] RSP: 
0018:ffff880057ceba90  EFLAGS: 00010282
Jan 31 05:12:24 localhost kernel: [87276.970065] RAX: 0000000000000055 
RBX: 00000000290029b3 RCX: 00000000000000f6
Jan 31 05:12:24 localhost kernel: [87276.970153] RDX: 0000000000000000 
RSI: 0000000000000046 RDI: 0000000000000202
Jan 31 05:12:24 localhost kernel: [87276.970240] RBP: ffff880057cebb00 
R08: 000000000000000a R09: 0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.970330] R10: 0000000000000000 
R11: 0000000000000001 R12: ffff88010e9d9b40
Jan 31 05:12:24 localhost kernel: [87276.970419] R13: 00000000000006e9 
R14: 0000000029003101 R15: 000000000000002a
Jan 31 05:12:24 localhost kernel: [87276.970507] FS:  
0000000000000000(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.970610] CS:  0010 DS: 0000 ES: 
0000 CR0: 000000008005003b
Jan 31 05:12:24 localhost kernel: [87276.970681] CR2: 0000000001c63018 
CR3: 000000005ad52000 CR4: 00000000000006e0
Jan 31 05:12:24 localhost kernel: [87276.970769] DR0: 0000000000000000 
DR1: 0000000000000000 DR2: 0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.970856] DR3: 0000000000000000 
DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 31 05:12:24 localhost kernel: [87276.970945] Process btrfs-endio-wri 
(pid: 15299, threadinfo ffff880057cea000, task ffff880103cb1c80)
Jan 31 05:12:24 localhost kernel: [87276.971056] Stack:
Jan 31 05:12:24 localhost kernel: [87276.971087]  0000000000000466 
00000000000006b4 0000000000000477 ffff88010e9d9b40
Jan 31 05:12:24 localhost kernel: [87276.971206]  ffff88010e9d9b40 
0000000000000000 0000160000000000 0000000000000000
Jan 31 05:12:24 localhost kernel: [87276.971286]  0000000000001000 
ffff880057cebc7c ffff88010e9d9b40 00000000000006e9
Jan 31 05:12:24 localhost kernel: [87276.971286] Call Trace:
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa0198251>] 
setup_items_for_insert+0x181/0x350 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01985e5>] 
btrfs_insert_empty_items+0xb5/0xe0 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01b8940>] 
insert_reserved_file_extent.constprop.52+0xc0/0x270 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01b98fa>] 
btrfs_finish_ordered_io+0x2ca/0x320 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01b999d>] 
btrfs_writepage_end_io_hook+0x4d/0xf0 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01cf03f>] 
end_bio_extent_writepage+0x12f/0x170 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff8119ba0d>] 
bio_endio+0x1d/0x40
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01ac736>] 
end_workqueue_fn+0x56/0x140 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01dc920>] 
worker_loop+0x150/0x520 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffffa01dc7d0>] ? 
btrfs_queue_worker+0x300/0x300 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff810883fc>] 
kthread+0x8c/0xa0
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff8142b874>] 
kernel_thread_helper+0x4/0x10
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff81088370>] ? 
kthread_worker_fn+0x190/0x190
Jan 31 05:12:24 localhost kernel: [87276.971286]  [<ffffffff8142b870>] ? 
gs_change+0x13/0x13
Jan 31 05:12:24 localhost kernel: [87276.971286] Code: 41 5f 5d c3 48 89 
da 48 c7 c7 c0 91 20 a0 31 c0 e8 94 9b 24 e1 0f 0b 48 89 c6 48 89 da 48 
c7 c7 80 91 20 a0 31 c0 e8 7e 9b 24 e1 <0f> 0b 0f 1f 40 00 55 48 89 e5 
48 83 ec 30 48 89 5d d8 4c 89 65
Jan 31 05:12:24 localhost kernel: [87276.971286] RIP  
[<ffffffffa01d535a>] memmove_extent_buffer+0x30a/0x310 [btrfs]
Jan 31 05:12:24 localhost kernel: [87276.971286]  RSP <ffff880057ceba90>
Jan 31 05:12:24 localhost kernel: [87276.993478] ---[ end trace 
174f2acd3ea6a532 ]---
Jan 31 05:12:24 localhost kernel: [87276.993491] note: 
btrfs-endio-wri[15299] exited with preempt_count 1

Re: btrfs bug

[Mitch Harder]

On Tue, Jan 31, 2012 at 11:20 PM, Thomas Weber
<thomas.weber.linux@googlemail.com> wrote:
> Hello Mitch,
>
> I have good news for you. I looked through all log files and found in the
> everything.log the following:
>
> Regards,
> Thomas
>
>
> Jan 31 05:12:24 localhost kernel: [87276.968049] btrfs memmove bogus
> src_offset 1870 move len 687876531 len 4096
> Jan 31 05:12:24 localhost kernel: [87276.968136] ------------[ cut here
> ]------------
> Jan 31 05:12:24 localhost kernel: [87276.968222] kernel BUG at
> fs/btrfs/extent_io.c:4357!
> Jan 31 05:12:24 localhost kernel: [87276.968296] invalid opcode: 0000 [#1]
> PREEMPT SMP

[...snip...]

This is coming from a BUG_ON(1) in the memcpy_extent_buffer() function
in extent_io.c

	if (src_offset + len > dst->len) {
		printk(KERN_ERR "btrfs memmove bogus src_offset %lu move "
		       "len %lu dst len %lu\n", src_offset, len, dst->len);
		BUG_ON(1);
	}

So, since (1870 + 687876531) > 4096, the BUG_ON was triggered.

There are two calls to memcpy_extent_buffer() from
setup_items_for_insert (the next function back in the callback shown
from the BUG_ON), so that part makes sense, at least.

I don't know if anybody else has anything to say on this, but my best
guess is that this btrfs volume has picked up some corruptions that
are feeding in some bad values.

btrfs bug

[Augusto]

Hello.
Thanks for read that message.
I see an bug when using dm-writecache in BTRFS.
I not see where to post about bug it.
I not wait support. Only report the bug.

If correct way to report bug not is with you ... please excuse me.
Have an nice week.

BTRFS Bug

[Ross Moore]

Hi,

I have a BTRFS filesystem that seems to be suffering from a few
problems. I'll post the first one, which looks most bizarre to me.

The filesystem is mounted at /media/Media. It consists of 4 devices in
RAID1 (both metadata and data), of sizes 3*2TB and 1*1TB. The result
of sudo btrfs fi df /media/Media/ is as follows:
Data, RAID1: total=3.06TB, used=8.74TB
System, RAID1: total=32.00MB, used=1.81MB
System: total=4.00MB, used=0.00
Metadata, RAID1: total=130.29GB, used=9.41GB

I'm running Ubuntu Quantal, on the stock 3.5 kernel (with stock
btrfs-tools), but the filesystem has been around for a over a year
now, since Oneiric or maybe Natty. It has been causing a few problems
recently with the odd kernel crash, but this line in bold seems the
most odd. It reports Total as smaller than Used. That just seems very
wrong to me. I'd also like to rescue my filesystem rather than kill it
and restore from backup if possible (since it's pretty big and
restoring would take a while / be error-prone).

I'm no kernel developer, but I am able  to compile and and willing to
help debug issues given instructions.

I also have the following mentions of btrfs in the syslog following boot:
Nov 12 22:10:43 HomeServer kernel: [    6.756770] btrfs: bdev
/dev/disk/by-uuid/f2178b12-fa9c-4fa0-9efb-11ad188156c0 errs: wr 0, rd
0, flush 0, corrupt 0, gen 0
Nov 12 22:10:43 HomeServer kernel: [   14.613574] btrfs: bdev /dev/sdd
errs: wr 72, rd 0, flush 0, corrupt 0, gen 0
Nov 12 22:10:43 HomeServer kernel: [   14.613578] btrfs: bdev /dev/sdc
errs: wr 542570, rd 559160, flush 0, corrupt 891, gen 0
Nov 12 22:10:43 HomeServer kernel: [   14.613582] btrfs: bdev /dev/sdb
errs: wr 156, rd 1166758, flush 0, corrupt 0, gen 0
Nov 12 22:10:43 HomeServer kernel: [   14.613584] btrfs: bdev /dev/sda
errs: wr 44273, rd 2378244, flush 0, corrupt 429, gen 0

If I attempt to rebalance, the kernel crashes after a while, well
before it has had a chance to complete.

Any assistance greatly appreciated, and I hope I can also help
identify a bug with help.

Thanks,
Ross

Re: BTRFS Bug

[Liu Bo]

On Mon, Nov 12, 2012 at 10:37:58PM +0800, Ross Moore wrote:
> Hi,
> 
> I have a BTRFS filesystem that seems to be suffering from a few
> problems. I'll post the first one, which looks most bizarre to me.
> 
> The filesystem is mounted at /media/Media. It consists of 4 devices in
> RAID1 (both metadata and data), of sizes 3*2TB and 1*1TB. The result
> of sudo btrfs fi df /media/Media/ is as follows:
> Data, RAID1: total=3.06TB, used=8.74TB
> System, RAID1: total=32.00MB, used=1.81MB
> System: total=4.00MB, used=0.00
> Metadata, RAID1: total=130.29GB, used=9.41GB
> 
> I'm running Ubuntu Quantal, on the stock 3.5 kernel (with stock
> btrfs-tools), but the filesystem has been around for a over a year
> now, since Oneiric or maybe Natty. It has been causing a few problems
> recently with the odd kernel crash, but this line in bold seems the
> most odd. It reports Total as smaller than Used. That just seems very
> wrong to me. I'd also like to rescue my filesystem rather than kill it
> and restore from backup if possible (since it's pretty big and
> restoring would take a while / be error-prone).
> 

Can you provide the output of 'btrfs-debug-tree /dev/sdd'?

thanks,
liubo

> I'm no kernel developer, but I am able  to compile and and willing to
> help debug issues given instructions.
> 
> I also have the following mentions of btrfs in the syslog following boot:
> Nov 12 22:10:43 HomeServer kernel: [    6.756770] btrfs: bdev
> /dev/disk/by-uuid/f2178b12-fa9c-4fa0-9efb-11ad188156c0 errs: wr 0, rd
> 0, flush 0, corrupt 0, gen 0
> Nov 12 22:10:43 HomeServer kernel: [   14.613574] btrfs: bdev /dev/sdd
> errs: wr 72, rd 0, flush 0, corrupt 0, gen 0
> Nov 12 22:10:43 HomeServer kernel: [   14.613578] btrfs: bdev /dev/sdc
> errs: wr 542570, rd 559160, flush 0, corrupt 891, gen 0
> Nov 12 22:10:43 HomeServer kernel: [   14.613582] btrfs: bdev /dev/sdb
> errs: wr 156, rd 1166758, flush 0, corrupt 0, gen 0
> Nov 12 22:10:43 HomeServer kernel: [   14.613584] btrfs: bdev /dev/sda
> errs: wr 44273, rd 2378244, flush 0, corrupt 429, gen 0
> 
> If I attempt to rebalance, the kernel crashes after a while, well
> before it has had a chance to complete.
> 
> Any assistance greatly appreciated, and I hope I can also help
> identify a bug with help.
> 
> Thanks,
> Ross
> --
> 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

Re: BTRFS Bug

[Ross Moore]

That's a big file - is that a dump of all the metadata? It's around
800MB. Two files provided, one with the errors/warnings, one the
actual output. Time-limited link to download, can you let me know when
you have downloaded a copy please?

http://akiajwevbuo5lh2yiu7q.sharing.s3.amazonaws.com/btrfs-debug-tree?AWSAccessKeyId=AKIAJWEVBUO5LH2YIU7Q&Expires=1352934869&Signature=LAX0noCgddqJY3pmfYh9v1moFqg%3D

http://akiajwevbuo5lh2yiu7q.sharing.s3.amazonaws.com/btrfs-debug-tree_errors?AWSAccessKeyId=AKIAJWEVBUO5LH2YIU7Q&Expires=1352934869&Signature=no9GxLnaaS1gc%2BBLJmxSlAAmNz0%3D

On 12 November 2012 23:08, Liu Bo <bo.li.liu@oracle.com> wrote:
> On Mon, Nov 12, 2012 at 10:37:58PM +0800, Ross Moore wrote:
>> Hi,
>>
>> I have a BTRFS filesystem that seems to be suffering from a few
>> problems. I'll post the first one, which looks most bizarre to me.
>>
>> The filesystem is mounted at /media/Media. It consists of 4 devices in
>> RAID1 (both metadata and data), of sizes 3*2TB and 1*1TB. The result
>> of sudo btrfs fi df /media/Media/ is as follows:
>> Data, RAID1: total=3.06TB, used=8.74TB
>> System, RAID1: total=32.00MB, used=1.81MB
>> System: total=4.00MB, used=0.00
>> Metadata, RAID1: total=130.29GB, used=9.41GB
>>
>> I'm running Ubuntu Quantal, on the stock 3.5 kernel (with stock
>> btrfs-tools), but the filesystem has been around for a over a year
>> now, since Oneiric or maybe Natty. It has been causing a few problems
>> recently with the odd kernel crash, but this line in bold seems the
>> most odd. It reports Total as smaller than Used. That just seems very
>> wrong to me. I'd also like to rescue my filesystem rather than kill it
>> and restore from backup if possible (since it's pretty big and
>> restoring would take a while / be error-prone).
>>
>
> Can you provide the output of 'btrfs-debug-tree /dev/sdd'?
>
> thanks,
> liubo
>
>> I'm no kernel developer, but I am able  to compile and and willing to
>> help debug issues given instructions.
>>
>> I also have the following mentions of btrfs in the syslog following boot:
>> Nov 12 22:10:43 HomeServer kernel: [    6.756770] btrfs: bdev
>> /dev/disk/by-uuid/f2178b12-fa9c-4fa0-9efb-11ad188156c0 errs: wr 0, rd
>> 0, flush 0, corrupt 0, gen 0
>> Nov 12 22:10:43 HomeServer kernel: [   14.613574] btrfs: bdev /dev/sdd
>> errs: wr 72, rd 0, flush 0, corrupt 0, gen 0
>> Nov 12 22:10:43 HomeServer kernel: [   14.613578] btrfs: bdev /dev/sdc
>> errs: wr 542570, rd 559160, flush 0, corrupt 891, gen 0
>> Nov 12 22:10:43 HomeServer kernel: [   14.613582] btrfs: bdev /dev/sdb
>> errs: wr 156, rd 1166758, flush 0, corrupt 0, gen 0
>> Nov 12 22:10:43 HomeServer kernel: [   14.613584] btrfs: bdev /dev/sda
>> errs: wr 44273, rd 2378244, flush 0, corrupt 429, gen 0
>>
>> If I attempt to rebalance, the kernel crashes after a while, well
>> before it has had a chance to complete.
>>
>> Any assistance greatly appreciated, and I hope I can also help
>> identify a bug with help.
>>
>> Thanks,
>> Ross
>> --
>> 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

Re: BTRFS Bug

[Sem]

Ross Moore <ross <at> rossmoore.net> writes:

[...]
> >> It reports Total as smaller than Used. That just seems very
> >> wrong to me. I'd also like to rescue my filesystem rather than kill it
> >> and restore from backup if possible (since it's pretty big and
> >> restoring would take a while / be error-prone).
> >>


I think this is the same problem I am having. I really do not want to restore
from backup because it is a lot of data and will therefore involve a van. Pls
post solution if you find it, thx.

Re: BTRFS Bug

[Liu Bo]

On Tue, Nov 20, 2012 at 05:54:35PM +0800, Ross Moore wrote:
> Hi,
> Any update on this before I wipe the disks and start again?

Hi Ross,

Sorry but I failed to reproduce it locally, although I've tried various
disk operations like balance, dev add/del etc...

So have you also tried the latest btrfs or the last stable one?
Does they show the same 'btrfs fi df' output?

thanks,
liubo

Re: BTRFS Bug

[Liu Bo]

On Tue, Nov 20, 2012 at 09:25:02PM +0800, Ross Moore wrote:
> Strange. Does that imply a problem with disks or disk cables physically?
> Our just the data rather than the metadata?
> 

It seems to be a kernel bug since another user also reported it sometime ago.

> I've compiled the latest btrfs-tools from git trunk add of a week ago when
> I reported the bug, same results. I haven't tried an updated kernel, just
> the 3.5. Should I upgrade to 3.7 rc? Will that hold any hope of change?

To be honest, I'm not sure if it'll help.

Hope that others can come up with where goes wrong.

thanks,
liubo

> On 20 Nov 2012 21:20, "Liu Bo" <bo.li.liu@oracle.com> wrote:
> 
> > On Tue, Nov 20, 2012 at 05:54:35PM +0800, Ross Moore wrote:
> > > Hi,
> > > Any update on this before I wipe the disks and start again?
> >
> > Hi Ross,
> >
> > Sorry but I failed to reproduce it locally, although I've tried various
> > disk operations like balance, dev add/del etc...
> >
> > So have you also tried the latest btrfs or the last stable one?
> > Does they show the same 'btrfs fi df' output?
> >
> > thanks,
> > liubo
> >

btrfs bug

[Maciej Sujkowski]

Hi All

I've been using btrfs for some time already however recently the
filesystem got corrupted somehow.
Currently when I try to mount the filesystem the following error
message is displayed and after few seconds system freezes completely:

[  250.620511] ------------[ cut here ]------------
[  250.620525] kernel BUG at
/home/kernel-ppa/COD/linux/fs/btrfs/extent-tree.c:1418!
[  250.620532] invalid opcode: 0000 [#1] SMP
[  250.620540] last sysfs file: /sys/devices/virtual/bdi/btrfs-2/uevent
[  250.620545] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat
binfmt_misc vboxnetadp vboxnetflt vboxdrv nfsd lockd nfs_acl
auth_rpcgss sunrpc kvm_amd kvm snd_hda_codec_hdmi snd_hda_codec_analog
arc4 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi
snd_rawmidi snd_seq_midi_event snd_seq p54usb p54common snd_timer
snd_seq_device crc_ccitt mac80211 nv_tco snd ppdev soundcore cfg80211
snd_page_alloc parport_pc psmouse lp asus_atk0110 serio_raw
i2c_nforce2 k8temp parport usb_storage usbhid hid uas pata_amd
forcedeth sata_nv dmfe raid10 raid456 async_raid6_recov async_pq
raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath
linear btrfs zlib_deflate libcrc32c
[  250.620648]
[  250.620654] Pid: 2402, comm: mount Not tainted 2.6.39-999-generic
#201105161320 System manufacturer System Product Name/M2NPV-VM
[  250.620668] EIP: 0060:[<f80fffbd>] EFLAGS: 00010202 CPU: 0
[  250.620716] EIP is at lookup_inline_extent_backref+0x46d/0x490 [btrfs]
[  250.620723] EAX: 00000001 EBX: 00000001 ECX: f376e000 EDX: 00000002
[  250.620729] ESI: f6b7d030 EDI: f376e000 EBP: f1e33a30 ESP: f1e339c4
[  250.620736]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[  250.620743] Process mount (pid: 2402, ti=f1e32000 task=f1cc8ca0
task.ti=f1e32000)
[  250.620749] Stack:
[  250.620752]  f376e000 ffffffff 00000001 00000000 f72dc098 f72dc07c
f1017e18 f376e000
[  250.620766]  f1e12000 078f3fff 00000000 f1017e28 078f3fff 00000000
00000000 ffffffff
[  250.620779]  f813491a 000000b0 00000000 00001001 0004a060 a8000000
00001000 00000000
[  250.620793] Call Trace:
[  250.620855]  [<f813491a>] ? set_extent_dirty+0x4a/0x60 [btrfs]
[  250.620904]  [<f8100359>] lookup_extent_backref+0x89/0x150 [btrfs]
[  250.620952]  [<f81032f1>] __btrfs_free_extent+0xc1/0x700 [btrfs]
[  250.621002]  [<f8103b23>] run_delayed_tree_ref+0x1f3/0x200 [btrfs]
[  250.621050]  [<f8103d94>] run_one_delayed_ref+0x54/0xf0 [btrfs]
[  250.621098]  [<f8103ecc>] run_clustered_refs+0x9c/0x1e0 [btrfs]
[  250.621147]  [<f81040ba>] btrfs_run_delayed_refs+0xaa/0x1d0 [btrfs]
[  250.621200]  [<f8111aa9>] btrfs_should_end_transaction+0x69/0x70 [btrfs]
[  250.621248]  [<f81043b3>] btrfs_drop_snapshot+0x1d3/0x540 [btrfs]
[  250.621307]  [<f8158789>] merge_reloc_roots+0xa9/0x120 [btrfs]
[  250.621367]  [<f815a8cd>] btrfs_recover_relocation+0x32d/0x3c0 [btrfs]
[  250.621421]  [<f8110bf8>] open_ctree+0x12f8/0x1460 [btrfs]
[  250.621471]  [<f810d410>] ? btree_writepage+0x110/0x110 [btrfs]
[  250.621493]  [<c1150001>] ? get_source+0x51/0x80
[  250.621505]  [<c12846ed>] ? snprintf+0x1d/0x20
[  250.621545]  [<f80ed72c>] btrfs_fill_super+0x5c/0x110 [btrfs]
[  250.621553]  [<c1281dc9>] ? strlcpy+0x39/0x50
[  250.621596]  [<f80f0fe3>] btrfs_mount+0x2e3/0x360 [btrfs]
[  250.621620]  [<c113082e>] mount_fs+0x3e/0x170
[  250.621641]  [<c114768c>] vfs_kern_mount+0x4c/0x90
[  250.621656]  [<c114833e>] do_kern_mount+0x3e/0x80
[  250.621663]  [<c1149765>] do_new_mount+0x55/0x80
[  250.621670]  [<c1149a38>] do_mount+0x188/0x1a0
[  250.621678]  [<c1149abd>] sys_mount+0x6d/0xa0
[  250.621689]  [<c152fe5f>] sysenter_do_call+0x12/0x28
[  250.621694] Code: 87 1f ff ff ff 39 c6 8d b4 26 00 00 00 00 0f 82
09 fe ff ff e9 0b ff ff ff bb f5 ff ff ff e9 7a fe ff ff 0f 0b eb fe
0f 0b eb fe <0f> 0b eb fe 31 db e9 58 fe ff ff ba b0 05 00 00 b8 50 fd
15 f8
[  250.621765] EIP: [<f80fffbd>]
lookup_inline_extent_backref+0x46d/0x490 [btrfs] SS:ESP 0068:f1e339c4
[  250.621811] ---[ end trace 107ba8e4b5f4d7fb ]---

Let me know if you need any additional information.

Regards
Maciek