btrfs Bug?

2010-04-06 Thread yoost...@netzero.com
Background:
Was checking E-mail and browsing the internet when suddenly Pidgin crashed out. 
I thought that was pretty weird so I went to go re-start Pidgin when I noticed 
the machine hang really hard for about 30 seconds. The machine finally came 
back and that's when I noticed that my E-mail client (Claws Mail) had stopped 
responding. I 'touch'ed a file in my home dir and that was fine, but then I 
went to md5sum a large file and it came back with an I/O error. I ran dmesg and 
found that there had been a kernel dump (or whatever the proper term is) 
related to BTRFS. I went to shut down my programs gracefully and do a reboot, 
unfortunately none of my programs (FF, Pidgin, Claws-Mail, one or two others) 
wanted to respond so I just used the power-button.

I switched my Intel X-25M (2nd gen, latest FW as of about a month ago) to a 
different SATA cable and on a different port on the motherboard (Supermicro 
C2SBX) to see if there was some sort of hardware problem there. I booted again 
into Gentoo and the boot failed (I'm guessing it failed after trying to mount 
the root partition as RO the first time).

I booted in to System Rescue CD 1.5.1 and tried to mount the partition and 
mount returned with a SegFault and dmesg spit out the following:

[code]

[   75.218065] device label root devid 1 transid 4446 /dev/sda3
[   75.225843] btrfs: sda3 checksum verify failed on 42488987648 wanted 
FC733AC3 found F7794308 level 1
[   75.226049] btrfs: sda3 checksum verify failed on 42488987648 wanted 
FC733AC3 found F7794308 level 1
[   75.226238] btrfs: sda3 checksum verify failed on 42488987648 wanted 
FC733AC3 found F7794308 level 1
[   75.226271] Btrfs detected SSD devices, enabling SSD mode
[   75.226490] [ cut here ]
[   75.226492] kernel BUG at fs/btrfs/extent-tree.c:3541!
[   75.226494] invalid opcode:  [#1] SMP
[   75.226497] last sysfs file: /sys/kernel/uevent_seqnum
[   75.226499] CPU 0
[   75.226500] Modules linked in: video nvidiafb output shpchp pci_hotplug 
hid_apple i2c_i801 processor button container i2c_core pcspkr psmouse serio_raw 
vgastate evdev iTCO_wdt iTCO_vendor_support x38_edac edac_core raid10 raid456 
async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 
raid0 multipath linear md_mod sg sd_mod sr_mod crc_t10dif cdrom usbhid hid 
uhci_hcd ahci libata e1000e ehci_hcd scsi_mod thermal usbcore thermal_sys
[   75.226534] Pid: 1804, comm: mount Not tainted 2.6.32.10-std151-amd64 #1 
C2SBX
[   75.226536] RIP: 0010:[]  [] 
btrfs_pin_extent+0x28/0xab
[   75.226545] RSP: 0018:88013abeba48  EFLAGS: 00010246
[   75.226547] RAX:  RBX: 0009e492c000 RCX: 0007c1bf
[   75.226549] RDX:  RSI: 88013a93e000 RDI: 4000
[   75.226552] RBP: 1000 R08: 88013abebb68 R09: 00080050
[   75.226554] R10: 027c R11: 000338c6 R12: 88013a414000
[   75.226556] R13:  R14:  R15: 812cb15f
[   75.226564] FS:  () GS:88000540(0063) 
knlGS:f75e4b60
[   75.226566] CS:  0010 DS: 002b ES: 002b CR0: 8005003b
[   75.226568] CR2: f76b2890 CR3: 00013b324000 CR4: 06f0
[   75.226570] DR0:  DR1:  DR2: 
[   75.226572] DR3:  DR6: 0ff0 DR7: 0400
[   75.226574] Process mount (pid: 1804, threadinfo 88013abea000, task 
88013ab71500)
[   75.226575] Stack:
[   75.226576]  880134781a20 88013abebb68 115f 
1000
[   75.226579] <0> 88013abebb68 812cb18b 88013abebb14 
880134781b40
[   75.226582] <0> 88013dd8f800 812caa63 fffa 
0009e492c000
[   75.226585] Call Trace:
[   75.226589]  [] ? process_one_buffer+0x2c/0x5e
[   75.226592]  [] ? walk_down_log_tree+0x2c3/0x362
[   75.226595]  [] ? walk_log_tree+0x78/0x183
[   75.226598]  [] ? join_transaction+0x174/0x1a0
[   75.226601]  [] ? btrfs_recover_log_trees+0x92/0x283
[   75.226603]  [] ? btree_get_extent+0x0/0x18b
[   75.226606]  [] ? process_one_buffer+0x0/0x5e
[   75.226609]  [] ? btree_read_extent_buffer_pages+0x65/0xa3
[   75.226612]  [] ? open_ctree+0xee5/0x1137
[   75.226615]  [] ? vsnprintf+0x3f4/0x42d
[   75.226619]  [] ? btrfs_get_sb+0x1ad/0x3a2
[   75.226623]  [] ? vfs_kern_mount+0x96/0x15b
[   75.226626]  [] ? do_kern_mount+0x49/0xe7
[   75.226629]  [] ? do_mount+0x73e/0x7a4
[   75.226633]  [] ? compat_sys_mount+0x1f6/0x231
[   75.226636]  [] ? ia32_sysret+0x0/0x5
[   75.226637] Code: 41 5d c3 41 56 41 55 41 89 cd 41 54 55 48 89 d5 53 4c 8b 
a7 28 01 00 00 48 89 f3 4c 89 e7 e8 d7 e1 ff ff 48 85 c0 49 89 c6 75 04 <0f> 0b 
eb fe 48 8b b8 90 00 00 00 48 81 c7 b8 00 00 00 e8 65 de
[   75.226658] RIP  [] btrfs_pin_extent+0x28/0xab
[   75.226662]  RSP 
[   75.226664] ---[ end trace 0ab19e2d653aad66 ]---
r...@sysresccd /root %
[/code]

I tried to mount it again 

Re: btrfs Bug?

2010-04-06 Thread yoost...@netzero.com
After reading around a bit on the btrfs wiki (the Getting_Started page and 
Gotchas page specifically) I found that I might be able to at least capture an 
image of the drive in case any devs needed to take a look at it; unfortunately 
btrfs-image failed with the same error.
I deduced that a repair of the FS requires it to be mounted with "mount -o 
degraded  ", but trying to mount in degraded mode also failed 
with the same error.
Not too sure where to go from here except shedding a tear for the few files 
that I didn't have backed up and starting over (or returning the drive? 
badblocks didn't return anything however..).


   Justin



Get Free Email with Video Mail & Video Chat!
http://www.netzero.net/freeemail?refcd=NZTAGOUT1FREM0210
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html