From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Linux Arch: kernel BUG at fs/btrfs/inode.c:873!
Date: Sat, 5 Oct 2013 04:42:56 +0000 (UTC) [thread overview]
Message-ID: <pan$29f84$2a19071e$4190bce2$1629fe10@cox.net> (raw)
In-Reply-To: CAOMFOmWzXL5G22Z7srkvXe+p+F9U7atOoiV5jRHc9i0k4kUfnA@mail.gmail.com
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@vger.kernel.org/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
next prev parent reply other threads:[~2013-10-05 4:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 4:03 Linux Arch: kernel BUG at fs/btrfs/inode.c:873! Anatol Pomozov
2013-10-05 4:42 ` Duncan [this message]
2013-10-05 11:51 ` Anatol Pomozov
2013-10-05 14:44 ` Duncan
2013-10-06 5:14 ` Anatol Pomozov
2013-10-06 10:10 ` Duncan
2013-10-08 6:36 ` Anatol Pomozov
2013-10-08 7:12 ` Liu Bo
2013-10-12 2:22 ` Anatol Pomozov
2013-10-12 21:20 ` Chris Murphy
2013-10-15 19:56 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$29f84$2a19071e$4190bce2$1629fe10@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox