Hide Forgot
Created attachment 482781 [details] xz'ed core file of btrfsck run I've had a number of oopses from btrfs related problems lately on 2.6.38, so I booted my laptop up to a live cd, installed btrfs-progs and ran btrfsck on the partition to see if it was corrupt. Here's what I get: # btrfsck /dev/sda3 bad key ordering 22 23 bad block 6571188224 btrfsck: btrfsck.c:2390: process_extent_item: Assertion `!(item_size != sizeof(*ei0))' failed. Aborted (core dumped) ...sadly, I'm going to have to rebuild the filesystem as I really need my laptop, but I saved off the core for analysis. The btrfs-progs version is: btrfs-progs-0.19-12.fc14.x86_64
Some thing similar in rawhide I have a luks encrypted /home dir that is formatted with btrfs. My laptop just crashes when it tries to mount my home dir. To see what was going on I remarked my /home dir in my fstab and then went through the steps preparing the partition for mounting (unlock luks, prep the logical volume etc) . Then just before mounting I ran a btrfs on the partition. It accepted that there was a btrfs file system there and checked for about 15 seconds before crashing. There may or may not be an issue with the filesystem but we shouldn't crash while checking it. Let me know if you want the core or any more info. ____________________________________________________________________ [root@pete ~]# btrfsck /dev/mapper/luks-5a12356f-3fc6-4685-8ee0-39da541a481f root 5 inode 66842 errors 400 root 5 inode 73393 errors 400 root 5 inode 73418 errors 400 root 5 inode 73433 errors 400 root 5 inode 73447 errors 400 root 5 inode 73482 errors 400 root 5 inode 73499 errors 400 root 5 inode 73511 errors 400 root 5 inode 73532 errors 400 root 5 inode 73544 errors 400 root 5 inode 120158 errors 400 root 5 inode 120160 errors 400 root 5 inode 120168 errors 400 root 5 inode 122203 errors 400 root 5 inode 122205 errors 400 root 5 inode 122213 errors 400 root 5 inode 298064 errors 400 root 258 root dir 256 error *** glibc detected *** btrfsck: double free or corruption (!prev): 0x0000000001dcfb10 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x78666)[0x7f919c087666] btrfsck[0x40c703] btrfsck[0x40164e] /lib64/libc.so.6(__libc_start_main+0xed)[0x7f919c03050d] btrfsck[0x401a19] ======= Memory map: ======== 00400000-00425000 r-xp 00000000 00:13 1102343 /sbin/btrfsck 00624000-00625000 rw-p 00024000 00:13 1102343 /sbin/btrfsck 01dc0000-01dec000 rw-p 00000000 00:00 0 [heap] 3d74e00000-3d74e15000 r-xp 00000000 00:13 862823 /lib64/libgcc_s-4.6.1-20110715.so.1 3d74e15000-3d75014000 ---p 00015000 00:13 862823 /lib64/libgcc_s-4.6.1-20110715.so.1 3d75014000-3d75015000 rw-p 00014000 00:13 862823 /lib64/libgcc_s-4.6.1-20110715.so.1 7f919c00f000-7f919c1b3000 r-xp 00000000 00:13 944887 /lib64/libc-2.14.90.so 7f919c1b3000-7f919c3b3000 ---p 001a4000 00:13 944887 /lib64/libc-2.14.90.so 7f919c3b3000-7f919c3b7000 r--p 001a4000 00:13 944887 /lib64/libc-2.14.90.so 7f919c3b7000-7f919c3b8000 rw-p 001a8000 00:13 944887 /lib64/libc-2.14.90.so 7f919c3b8000-7f919c3be000 rw-p 00000000 00:00 0 7f919c3be000-7f919c3c2000 r-xp 00000000 00:13 1060366 /lib64/libuuid.so.1.3.0 7f919c3c2000-7f919c5c1000 ---p 00004000 00:13 1060366 /lib64/libuuid.so.1.3.0 7f919c5c1000-7f919c5c2000 r--p 00003000 00:13 1060366 /lib64/libuuid.so.1.3.0 7f919c5c2000-7f919c5c3000 rw-p 00004000 00:13 1060366 /lib64/libuuid.so.1.3.0 7f919c5c3000-7f919c5e4000 r-xp 00000000 00:13 944880 /lib64/ld-2.14.90.so 7f919c7c4000-7f919c7c7000 rw-p 00000000 00:00 0 7f919c7e2000-7f919c7e4000 rw-p 00000000 00:00 0 7f919c7e4000-7f919c7e5000 r--p 00021000 00:13 944880 /lib64/ld-2.14.90.so 7f919c7e5000-7f919c7e6000 rw-p 00022000 00:13 944880 /lib64/ld-2.14.90.so 7f919c7e6000-7f919c7e7000 rw-p 00000000 00:00 0 7ffffe3f9000-7ffffe41a000 rw-p 00000000 00:00 0 [stack] 7ffffe51b000-7ffffe51c000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Aborted (core dumped) _____________________________________________________________________________ 3.1.0-0.rc0.git21.1.fc17.x86_64 #1 SMP Fri Aug 5 15:35:52 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux I have tried with 3 different kernels I have also tried with both btrfs-progs-0.19-14.fc17.x86_64 btrfs-progs-0.19-16.fc17.x86_64
Forgot glibc-2.14.90-4.x86_64
I found the thread on the mailing list about running btrfs-zero-log and the first time I ran it I got the following. I ran it again and it completed sucessfully. [root@pete ~]# btrfs-zero-log /dev/mapper/luks-5a12356f-3fc6-4685-8ee0-39da541a481f *** glibc detected *** btrfs-zero-log: double free or corruption (!prev): 0x00000000024f9b10 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x78666)[0x7fc1792a8666] btrfs-zero-log[0x407863] btrfs-zero-log[0x4013df] /lib64/libc.so.6(__libc_start_main+0xed)[0x7fc17925150d] btrfs-zero-log[0x4014a1] ======= Memory map: ======== 00400000-0041f000 r-xp 00000000 00:13 1103203 /sbin/btrfs-zero-log 0061e000-0061f000 rw-p 0001e000 00:13 1103203 /sbin/btrfs-zero-log 024ea000-028dd000 rw-p 00000000 00:00 0 [heap] 3d74e00000-3d74e15000 r-xp 00000000 00:13 862823 /lib64/libgcc_s-4.6.1-20110715.so.1 3d74e15000-3d75014000 ---p 00015000 00:13 862823 /lib64/libgcc_s-4.6.1-20110715.so.1 3d75014000-3d75015000 rw-p 00014000 00:13 862823 /lib64/libgcc_s-4.6.1-20110715.so.1 7fc179230000-7fc1793d4000 r-xp 00000000 00:13 944887 /lib64/libc-2.14.90.so 7fc1793d4000-7fc1795d4000 ---p 001a4000 00:13 944887 /lib64/libc-2.14.90.so 7fc1795d4000-7fc1795d8000 r--p 001a4000 00:13 944887 /lib64/libc-2.14.90.so 7fc1795d8000-7fc1795d9000 rw-p 001a8000 00:13 944887 /lib64/libc-2.14.90.so 7fc1795d9000-7fc1795df000 rw-p 00000000 00:00 0 7fc1795df000-7fc1795e3000 r-xp 00000000 00:13 1060366 /lib64/libuuid.so.1.3.0 7fc1795e3000-7fc1797e2000 ---p 00004000 00:13 1060366 /lib64/libuuid.so.1.3.0 7fc1797e2000-7fc1797e3000 r--p 00003000 00:13 1060366 /lib64/libuuid.so.1.3.0 7fc1797e3000-7fc1797e4000 rw-p 00004000 00:13 1060366 /lib64/libuuid.so.1.3.0 7fc1797e4000-7fc179805000 r-xp 00000000 00:13 944880 /lib64/ld-2.14.90.so 7fc1799e5000-7fc1799e8000 rw-p 00000000 00:00 0 7fc179a03000-7fc179a05000 rw-p 00000000 00:00 0 7fc179a05000-7fc179a06000 r--p 00021000 00:13 944880 /lib64/ld-2.14.90.so 7fc179a06000-7fc179a07000 rw-p 00022000 00:13 944880 /lib64/ld-2.14.90.so 7fc179a07000-7fc179a08000 rw-p 00000000 00:00 0 7fff480ce000-7fff480ef000 rw-p 00000000 00:00 0 [stack] 7fff481ff000-7fff48200000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Aborted (core dumped) ---------------------------------------------------------------------------- After that I was able to run an fsck with out crashing. But with lots of errors detected. _________________________________________________________________________ [root@pete ~]# btrfsck /dev/mapper/luks-5a12356f-3fc6-4685-8ee0-39da541a481f root 5 inode 66842 errors 400 root 5 inode 73393 errors 400 root 5 inode 73418 errors 400 root 5 inode 73433 errors 400 root 5 inode 73447 errors 400 root 5 inode 73482 errors 400 root 5 inode 73499 errors 400 root 5 inode 73511 errors 400 root 5 inode 73532 errors 400 root 5 inode 73544 errors 400 root 5 inode 120158 errors 400 root 5 inode 120160 errors 400 root 5 inode 120168 errors 400 root 5 inode 122203 errors 400 root 5 inode 122205 errors 400 root 5 inode 122213 errors 400 root 5 inode 298064 errors 400 root 258 root dir 256 error found 94704238592 bytes used err is 1 total csum bytes: 92282384 total tree bytes: 198377472 total fs tree bytes: 74080256 btree space waste bytes: 34120034 file data blocks allocated: 95459762176 referenced 94206832640 Btrfs Btrfs v0.19 ___________________________________________________________________ But at least I can now mount my /home dir
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping