From: LM <linux-raid@moellendorf.eu>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Assemble the previously replaced components of a previously created array into an active array
Date: Wed, 21 Jun 2017 22:15:36 +0200 [thread overview]
Message-ID: <20170621201536.GI14809@lars-laptop> (raw)
Hi,
I replaced all component devices of my RAID5 like in the example below:
mdadm /dev/md/test --add-spare /dev/loop20 --replace /dev/loop10 --with /dev/loop20
mdadm /dev/md/test --add-spare /dev/loop21 --replace /dev/loop11 --with /dev/loop21
mdadm /dev/md/test --add-spare /dev/loop22 --replace /dev/loop12 --with /dev/loop22
mdadm /dev/md/test --add-spare /dev/loop23 --replace /dev/loop13 --with /dev/loop23
mdadm /dev/md/test --remove /dev/loop10 /dev/loop11 /dev/loop12 /dev/loop13
Now one of my new disks failed. I currently rebuilding the RAID with the
failed disk hoping that the reason for failure has been resolved.
But I wonder if I could just:
1) power down the machine
2) replace all for disks by the removed old (and functioning) disks
3) assemble the old RAID
This would be a great relief, because no relevant data changed since the
replacement. However, the RAID has been in use during the replacement
and this makes me worry that the RAID cannot be assembled using the old
disks due to data inconsistency.
Best,
Lars
reply other threads:[~2017-06-21 20:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170621201536.GI14809@lars-laptop \
--to=linux-raid@moellendorf.eu \
--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