From: Chris Murphy <lists@colorremedies.com>
To: "Warren, Daniel" <daniel.warren@mcmcllc.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: attempt to mount after crash during rebalance hard crashes server
Date: Tue, 29 Mar 2016 14:46:19 -0600 [thread overview]
Message-ID: <CAJCQCtT7VD2r-gHBCDgCcicSgfhgFLQy-DXgWGGm4c76wtFTHQ@mail.gmail.com> (raw)
In-Reply-To: <CAHaDNyXRW4FQC+5P2_8apdFan2wtsHnPyzuK5ZPq8dLXW-S9_g@mail.gmail.com>
On Tue, Mar 29, 2016 at 2:21 PM, Warren, Daniel
<daniel.warren@mcmcllc.com> wrote:
> Greetings all,
>
> I'm running 4.4.0 from deb sid
>
> My server crashed during a balance after I had added 10 disks to the
> original 15, I have not been able to bring the FS up since, it causes
> a system crash
>
> btrfs fi sh looks fine, but when I mount , it crashes the server with
> a NULL pointer dereference error
> Each Disk in the set is LUKS encrypted
>
> btrfs fi sh http://pastebin.com/QLTqSU8L
> kernel panic http://pastebin.com/aBF6XmzA
Panic shows:
CPU: 0 PID: 153 Comm: kworker/u8:13 Not tainted 3.16-2-amd64 #1 Debian 3.16.3-2
That's old. Are you sure you're running 4.4.0?
> If it's of any use I can run tests before I attempt check --repair
I suggest 4.4.5 or newer, and just try a regular mount first. The
general sequence is: newer kernel regular mount, then -o recovery,
then -o ro, recovery, and then btrfs check without --repair, and
posting all of the messages from those attempts.
--
Chris Murphy
next prev parent reply other threads:[~2016-03-29 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 20:21 attempt to mount after crash during rebalance hard crashes server Warren, Daniel
2016-03-29 20:46 ` Chris Murphy [this message]
2016-03-29 21:25 ` Patrik Lundquist
2016-03-29 22:55 ` Duncan
2016-03-30 14:11 ` Warren, Daniel
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=CAJCQCtT7VD2r-gHBCDgCcicSgfhgFLQy-DXgWGGm4c76wtFTHQ@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=daniel.warren@mcmcllc.com \
--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;
as well as URLs for NNTP newsgroup(s).