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@xxxxxxxxxxxxxxxxxxxxxx
F: +61 2 8304 0001 www.websitemanagers.com.au
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
