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 18:00:04 +0500 [thread overview]
Message-ID: <20160407180004.53615913@natsu> (raw)
In-Reply-To: <1460033086.27740.145.camel@interlinx.bc.ca>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Thu, 07 Apr 2016 08:44:46 -0400
"Brian J. Murrell" <brian@interlinx.bc.ca> wrote:
> # cat /proc/mdstat
> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
> md0 : active raid1 sdd[0]
> 1953514496 blocks [2/1] [U_]
>
> md1 : active raid0 sdc[1] sdb[0]
> 1953524736 blocks super 1.2 512k chunks
...
> Is my only option here to fail/remove /dev/md1 from the array and re-
> add it that way or is there a more graceful recovery possible here?
You do not have a write intent bitmap at md0, so re-add will not work. Seems
like you should --add it now, then after it rebuilds use --grow to add a
bitmap, so that in the future you could use -re-add.
As to why the situation occured in the first place, you should ensure that md1
assembles before md0. Perhaps by listing both arrays in /etc/mdadm/mdadm.conf
in the order you need (and don't forget to re-generate initrd.img).
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-04-07 13:00 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 [this message]
2016-04-07 16:11 ` Brian J. Murrell
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=20160407180004.53615913@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 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.