Anatol Pomozov posted on Fri, 04 Oct 2013 21:03:11 -0700 as excerpted: > Hi, > > I have a home server on Linux Arch (kernel 3.11.2) that uses > multi-device btrfs on root filesystem. > > Until recently it worked completely fine. And yesterday I rebooted it > and the machine did not wake up. > > I booted from a USB (kernel 3.10) and tried to mount the filesystem. > Here is OOPs I see > ------------[ cut here ]------------ > [ 68.126138] kernel BUG at fs/btrfs/inode.c:873! > [ 68.126164] invalid opcode: 0000 [#1] PREEMPT SMP > The only thing that I did recently is defrag /var/log/journal files > (journalctl is very slow because of btrfs COW). Something like this > http://www.mail-archive.com/linux-btrfs@xxxxxxxxxxxxxxx/msg24878.html > > How to fix this problem? And restore the data... I'm not a dev just a btrfs user and list regular myself, so the traces don't mean much to me. However, the bit I retained in the quote above (especially the 0000 opcode) looks very much like a bug that should be fixed in kernel 3.12, with the patch queued for stable as well, but due to a mixup it didn't get into stable thru 3.11.4, but the mixup's hopefully straightened out now so with luck it'll be in 3.11.5. So the first thing I'd try is either cherrypicking the btrfs patches from 3.12 back to 3.11-stable, or wait for 3.11.5 and check for btrfs patches there, or try 3.12-rcX (rc3 is out and I guess rc4 should be out shortly now as I think it has been nearly a week). With luck that'll fix it. If not, then post back with the new kernel you tried and hopefully one of the devs can help. -- 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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
