From: Roman Mamedov <rm@romanrm.net>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid1 recoverable after system crash?
Date: Thu, 7 Apr 2016 21:59:27 +0500 [thread overview]
Message-ID: <20160407215927.2fc82680@natsu> (raw)
In-Reply-To: <1460045497.27740.157.camel@interlinx.bc.ca>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
On Thu, 07 Apr 2016 12:11:37 -0400
"Brian J. Murrell" <brian@interlinx.bc.ca> wrote:
> 2016 Apr 7 12:01:00 linux [16583.606363] md/raid1:md0: Disk failure on md1, disabling device.
> 2016 Apr 7 12:01:00 linux [16583.606366] md/raid1:md0: Operation continuing on 1 devices.
> 2016 Apr 7 12:01:00 linux FailSpare event detected on md device /dev/md0, component device /dev/md1
> 2016 Apr 7 12:01:01 linux [16583.907982] BUG: unable to handle kernel paging request at 0000000099b899b8
> 2016 Apr 7 12:01:01 linux [16583.908009] IP: [<ffffffffa0019227>] call_bio_endio+0x37/0xb0 [raid1]
> 2016 Apr 7 12:01:01 linux [16583.908009] Oops: 0000 [#1] SMP
> 2016 Apr 7 12:01:01 linux [16583.908009] Stack:
> 2016 Apr 7 12:01:01 linux [16583.908009] Call Trace:
> 2016 Apr 7 12:01:01 linux [16583.908009] Code: 4c 89 65 e0 4c 89 6d e8 4c 89 75 f0 4c 89 7d f8 66 66 66 66 90 4c 8b 67 28 48 8b 47 20 41 bf 01 00 00 00 48 89 fb 41 8b 54 24 2c <4c> 8b 28 85 d2 75 42 48 8b 43 18 a8 01 75 07 3e 41 80 64 24 18
> 2016 Apr 7 12:01:01 linux [16583.908009] RIP [<ffffffffa0019227>] call_bio_endio+0x37/0xb0 [raid1]
> 2016 Apr 7 12:01:01 linux [16583.908009] CR2: 0000000099b899b8
>
> And it seems to be stuck there now.
>
> dmesg contents at http://www.interlinx.bc.ca/~brian/raid-dmesg.txt
Don't know what's up with this bug, maybe someone else does.
How are the drives connected, plain SATA, not something unusual such as USB?
As something to try, upgrade to a newer kernel if you can: the 3.2 series is
very old, maybe the bug has been fixed in newer ones.
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-04-07 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 12:44 raid1 recoverable after system crash? Brian J. Murrell
2016-04-07 13:00 ` Roman Mamedov
2016-04-07 16:11 ` Brian J. Murrell
2016-04-07 16:59 ` Roman Mamedov [this message]
2016-04-07 17:10 ` Brian J. Murrell
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=20160407215927.2fc82680@natsu \
--to=rm@romanrm.net \
--cc=brian@interlinx.bc.ca \
--cc=linux-raid@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).