From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Rich Freeman <r-btrfs@gw.thefreemanclan.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: unable to handle kernel paging request - btrfs
Date: Thu, 22 Sep 2016 14:44:44 +0200 [thread overview]
Message-ID: <57E3D23C.3050905@applied-asynchrony.com> (raw)
In-Reply-To: <CAGfcS_m0KvAjmWpnGC7agLYBKROqjPoSCVrziaEJXzW1Dyw5iQ@mail.gmail.com>
On 09/22/16 14:18, Rich Freeman wrote:
> I have been getting panics consistently after doing a btrfs replace
> operation on a raid1 and rebooting. I linked a photo of the panic; I
> haven't been able to get a text capture of it.
>
> https://ibin.co/2vx0HhDeViu3.jpg
>
> I'm getting this error on the latest 4.4, 4.1, and even on an old
> 3.18.26 kernel I had lying around.
What happens when you try to boot e.g. SystemRescueCD?
If it is what I think it is (see below) then that should start bombing
as well.
> I'm able to boot into single-user mode and if I don't start any
> processes the system seems fairly stable. I am also able to start a
> btrfs balance and run that for several hours without issue. If I
> start launching services the system will tend to panic, though how
> many processes I can launch will vary. I don't think that it is a
> particular file being accessed that is triggering the issue since the
> point where it fails varies. I suspect it may be load-related.
If the SystemRescue method does not work then you have either
an overheating/dying CPU or - more likely - bad memory.
Another - probably unlikely, but not impossible - option would be to
delete the swap file, if you have one. I've seen some super-strange
things with corrupt or incorrectly created swap *even if it isn't
heavily used*, right after boot. E.g. if your swapfile was fallocated
instead of dd'ed and lives on ext4 or XFS, you *must* use the -z option
to pre-touch all extents.
Or maybe it's the ghost of ZFS, if that's patched in as well.. :-)
-h
next prev parent reply other threads:[~2016-09-22 12:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 12:18 unable to handle kernel paging request - btrfs Rich Freeman
2016-09-22 12:44 ` Holger Hoffstätte [this message]
2016-09-22 16:23 ` David Sterba
2016-09-22 16:46 ` Rich Freeman
2016-09-22 17:29 ` Chris Murphy
2016-09-22 17:41 ` Jeff Mahoney
2016-09-30 18:54 ` Rich Freeman
2016-09-30 20:55 ` Jeff Mahoney
2016-09-30 21:07 ` Rich Freeman
2016-10-01 0:38 ` Jeff Mahoney
2016-10-07 14:00 ` Rich Freeman
2016-10-08 21:55 ` Rich Freeman
2016-10-10 12:54 ` Rich Freeman
2016-09-23 4:58 ` Duncan
2016-09-25 13:55 ` Rich Freeman
2016-09-26 0:22 ` Jeff Mahoney
2016-09-26 0:37 ` Rich Freeman
2016-09-26 0:39 ` Jeff Mahoney
2016-09-26 0:42 ` Rich Freeman
2016-09-26 2:21 ` Duncan
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=57E3D23C.3050905@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=r-btrfs@gw.thefreemanclan.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.