On Tue, Nov 29, 2011 at 04:29:54PM +0100, Karl Mardoff Kittilsen wrote: > Den 29. nov. 2011 16:12, skrev Chris Mason: > >On Tue, Nov 29, 2011 at 02:39:26AM +0100, Karl Mardoff Kittilsen wrote: > >>Hi! > >> > >>Sending a mail on this issue, as advised on IRC. > >> > >>My /home file system fails to mount and the kernel seem to freeze > >>and I need to do the Alt+SysRq RSNEIUB routine to boot it safely. > >>The corruption happened on a 3.2-rc<something> kernel and Ubuntu > >>11.10, but I am now running on Ubuntu 12.04 with the 3.2.0-2-generic > >>kernel to see if that helped, it did not. > >>btrfsck from the latest btrfs-tools returns: > >> > >>karl@karl-precise:~/git/btrfs-progs$ sudo ./btrfsck /dev/md0 > >>ref mismatch on [2176962560 8192] extent item 480, found 1 > >>Incorrect local backref count on 2176970752 root 5 owner 2101705 > >>offset 368640 found 1 wanted 3925868545 > >>backpointer mismatch on [2176970752 4096] > > > >So the crashes below were because we tried to free one of these extents. > >You have two extents whose reference counts are way off. > > > >Unfortunately this is stored on disk, so different kernels aren't going > >to fix it (yet). One of the extents is in a file with inode number > >2101705, and the other is in a btree block (2176962560). > > > >I'll be able to fix this soon, but we can also make a patch that changes > >those BUG_ONs to just deal with the mismatch. The worst case here would > >be leaking those two extents, about 12K of data. > > > >-chris > > Thank you for looking into it, and that does sounds really > promising. I am available to test any patches you want tested. Is > there anything else that I can do to help getting this issue fixed?
The good news about this one is that it is very clear cut. The hard part is figuring out where these bogus link counts came from. I'd suggest that you spend some time running memtest on the machine. -chris -- 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
