From: Adam Goryachev <mailinglists@websitemanagers.com.au>
To: jtroan@jt-sw.com, Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: Resurrecting a Dirty RAID-5
Date: Mon, 13 Jul 2015 08:33:09 +1000 [thread overview]
Message-ID: <55A2EB25.10607@websitemanagers.com.au> (raw)
In-Reply-To: <OF4E023A92.1624DC91-ON85257E80.0051B769-85257E80.005287C5@jt-sw.com>
On 13/07/15 01:01, jtroan@jt-sw.com wrote:
>> On Wed, 8 Jul 2015, jtroan@jt-sw.com wrote:
>>
>>> I'm also thinking about adding a fourth drive and try to config it as a
>>> hot-spare, giving me some extra margin for failure.
>> I would recommend you turn your raid5 into raid6 instead of having a
>> raid5+spare. This can be done with a fairly simple command, without
>> downtime.
>>
> I like the idea of using RAID-6 for / (for all the VMs under /var). (I
> figure I'll probably still have to do a spare on my RAID-1 device
> for /boot .)
>
> What's the (mdadm?) command to convert an MD from RAID-5 to RAID-6?
>
I think the standard option would be to have a hot spare, and then
something like:
mdadm /dev/mdX --grow --level=raid6
Also, for your raid1, never have a hot spare, just do this:
mdadm /dev/mdX --grow --raid-devices=3
Then you will always have all your data replicated on all three drives,
so again, no hot spare required.
Also remember to duplicate the grub/whatever boot sector....
Regards,
Adam
--
Adam Goryachev Website Managers www.websitemanagers.com.au
next prev parent reply other threads:[~2015-07-12 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:14 Resurrecting a Dirty RAID-5 jtroan
2015-07-08 13:19 ` Phil Turmel
2015-07-09 2:57 ` jtroan
2015-07-12 5:57 ` Mikael Abrahamsson
2015-07-12 15:01 ` jtroan
2015-07-12 22:33 ` Adam Goryachev [this message]
2015-07-13 6:31 ` Can Jeuleers
2015-07-13 7:15 ` Adam Goryachev
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=55A2EB25.10607@websitemanagers.com.au \
--to=mailinglists@websitemanagers.com.au \
--cc=jtroan@jt-sw.com \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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.