From: Adam Goryachev <adam@websitemanagers.com.au>
To: Can Jeuleers <can.jeuleers@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Resurrecting a Dirty RAID-5
Date: Mon, 13 Jul 2015 17:15:29 +1000 [thread overview]
Message-ID: <55A36591.8040004@websitemanagers.com.au> (raw)
In-Reply-To: <55A35B4B.9020706@gmail.com>
On 13/07/15 16:31, Can Jeuleers wrote:
> On 13/07/15 00:33, Adam Goryachev wrote:
>> 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.
> Never say never, as there are valid use cases for having hot spares in a
> RAID1 set.
>
> My own use case is that I want to be reasonably assured that my spare
> won't fail at around the same time as the active disks (due to having
> the same age and having been subjected to exactly the same workload).
Yes, this is true too... though with physical HDD, I would expect there
are enough differences to mean that they will fail at different times,
even SSD's should have enough variance.
Of course, the other option is to purchase the drives at different times
(eg, one month apart) so they are also from different batches, as well
as have a month or two difference in how they are used.
Of course, if both drives in the RAID1 fail at the exact same moment,
how is a hot spare better than a three drive raid1? Wouldn't the chance
of three drives failing at the same critical moment be less than the
chance of two drives failing at the same time (or one drive to fail, and
then the second to fail during the increased load of a resync)?
I really have no idea about the actual statistical numbers/chances, but
sounds like a valid question to me...
PS, of course, you should never say never, so I do still agree with you,
someone, somewhere might have a reason to do it differently. However, if
they really do, then they should know better than me.
Regards,
Adam
--
Adam Goryachev
Website Managers
P: +61 2 8304 0000 adam@websitemanagers.com.au
F: +61 2 8304 0001 www.websitemanagers.com.au
prev parent reply other threads:[~2015-07-13 7:15 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
2015-07-13 6:31 ` Can Jeuleers
2015-07-13 7:15 ` Adam Goryachev [this message]
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=55A36591.8040004@websitemanagers.com.au \
--to=adam@websitemanagers.com.au \
--cc=can.jeuleers@gmail.com \
--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.