From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-raid@vger.kernel.org
Subject: Re: raid1 recoverable after system crash?
Date: Thu, 07 Apr 2016 12:11:37 -0400 [thread overview]
Message-ID: <1460045497.27740.157.camel@interlinx.bc.ca> (raw)
In-Reply-To: <20160407180004.53615913@natsu>
[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]
On Thu, 2016-04-07 at 18:00 +0500, Roman Mamedov wrote:
>
> You do not have a write intent bitmap at md0, so re-add will not
> work.
Ahhh. OK.
> Seems
> like you should --add it now,
Tried that. It started off and got this far:
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 md1[2](F) sdd[0]
1953514496 blocks [2/1] [U_]
[================>....] recovery = 82.0% (1602507648/1953514496) finish=42613.2min speed=137K/sec
before hitting this:
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
> then after it rebuilds use --grow to add a
> bitmap, so that in the future you could use -re-add.
Cool. Will do, when this finally gets fixed.
> As to why the situation occured in the first place, you should ensure
> that md1
> assembles before md0.
Yeah. Just noticed as of this incident that the order in mdadm.conf is
wrong. :-(
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-07 16:11 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 [this message]
2016-04-07 16:59 ` Roman Mamedov
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=1460045497.27740.157.camel@interlinx.bc.ca \
--to=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).