From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: unable to handle kernel paging request - btrfs
Date: Mon, 26 Sep 2016 02:21:22 +0000 (UTC) [thread overview]
Message-ID: <pan$b52da$3be1bbf5$8f186275$d22036bc@cox.net> (raw)
In-Reply-To: CAGfcS_n+pMq0thNEM9b2ZA78xEpXTFJXjwTHRyvquLS8dR_yng@mail.gmail.com
Rich Freeman posted on Sun, 25 Sep 2016 09:55:42 -0400 as excerpted:
> On Fri, Sep 23, 2016 at 12:58 AM, Duncan <1i5t5.duncan@cox.net> wrote:
>>
>> Btrfs raid1 you say, and you have existing compressed files it's trying
>> to read in the backtrace?
>>
>> Sounds like the issues I see sometimes and have posted about where
>> after a crash that resulted in one device of my raid1 pair getting
>> behind the other, the kernel will crash if it sees too many
>> csum-errors, even tho it's /supposed/ to check the other copy and read
>> from it if valid (which it is as a btrfs scrub resolves the issue).
>>
>> When booted to rescue/single-user mode, can you run a scrub?
>
> After a few reboots trying to capture the initial panic message (even
> when I set panic_on_oops=1 I was getting multiple ones with only the
> tainted one staying on screen), the system managed to stay up. I
> completed a scrub and it found no errors.
Well, so much for that theory. If it found and fixed errors you'd likely
be seeing the same problem I see sometimes, but if it didn't find any to
fix... unlikely.
--
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
prev parent reply other threads:[~2016-09-26 2:21 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
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 [this message]
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$b52da$3be1bbf5$8f186275$d22036bc@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;
as well as URLs for NNTP newsgroup(s).