From: Wols Lists <antlists@youngman.org.uk>
To: Paul Dann <pdgiddie@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: mdadm RAID1 -> 5 conversion safety
Date: Wed, 5 Feb 2020 18:29:57 +0000 [thread overview]
Message-ID: <5E3B09A5.8010209@youngman.org.uk> (raw)
In-Reply-To: <CALZj-VqNACF+Dn5rBrLaVmvVE2weOAjqtvWpwKU7sE=72nyvXg@mail.gmail.com>
On 05/02/20 11:51, Paul Dann wrote:
> Hi there,
>
> I've got a load of data on an md RAID 1 array assembled from 2x4TB
> disks. I'm looking to expand this by adding a third 4TB disk and
> converting the array to RAID 5. Now the required procedure is
> documented on the wiki, but my question is:
>
> When I convert the RAID 1 array to RAID 5, the array will be in a
> degraded state as it rebuilds onto the new disk. However, if one of
> the original two disks were to fail during this procedure, is mdadm
> smart enough to convert the array back to degraded RAID 1, or will my
> array now be a broken RAID 5 with no path to recovery?
There is a "revert reshape" option which will take you back to a raid 1.
This assumes, however, that it's the new disk that has failed.
I'm pretty certain, however, that should one of the old disks fail
during the conversion you will end up with a degraded raid 5.
If you're worried, I would make sure you've done a SMART health check on
your two original drives, although that's no guarantee everything's okay.
If you really are that worried, get two new disks with the intention of
ending up at raid 6. Add a 3rd drive to the mirror, fail and remove one
of the originals, add the 4th to go raid 5, then add back the first to
go raid 6.
One thing I will say - MAKE SURE you have the latest mdadm, and if
possible make sure you're running a recent kernel. There have been
issues converting from 1 to 5. None of them serious, and all fixed by
upgrading mdadm/kernel, hence the advice to be running the latest/greatest.
>
> Many thanks,
> Paul
>
Cheers,
Wol
next prev parent reply other threads:[~2020-02-05 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 11:51 mdadm RAID1 -> 5 conversion safety Paul Dann
2020-02-05 18:29 ` Wols Lists [this message]
2020-02-06 22:41 ` NeilBrown
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=5E3B09A5.8010209@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=pdgiddie@gmail.com \
/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).