linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* mdadm - raid6 best practices ?
@ 2017-09-22  3:55 Nikhil Kshirsagar
  2017-09-22 18:26 ` Song Liu
  2017-09-23  0:40 ` Stan Hoeppner
  0 siblings, 2 replies; 6+ messages in thread
From: Nikhil Kshirsagar @ 2017-09-22  3:55 UTC (permalink / raw)
  To: Linux RAID

Hello linux-raid,

A customer has some questions about raid6 best practices. They are
using a 84-disk MD1280 Expansion Shelf (seagate disks). They want to
use mdadm to setup a s/w raid, using raid6.

The questions are

a) recommended number of disks included in RAID array set?
b) Is it possible to include all 84 disks in one array and leave 2 of
them as host spare?
c) Is there a raid6 best practices document to refer to ?

Can anyone point me to me any internal docs or articles to construct a
reply to the customer?

Thanks,
Nikhil.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: mdadm - raid6 best practices ?
  2017-09-22  3:55 mdadm - raid6 best practices ? Nikhil Kshirsagar
@ 2017-09-22 18:26 ` Song Liu
  2017-09-22 19:24   ` Wols Lists
  2017-09-23  0:40 ` Stan Hoeppner
  1 sibling, 1 reply; 6+ messages in thread
From: Song Liu @ 2017-09-22 18:26 UTC (permalink / raw)
  To: linux-raid; +Cc: nkshirsa, Song Liu

I would say this is a tradeoff between space overhead (2 parity disks per
array) and data reliability (mean time before data loss, MTBDL, or MTTF).
Space overhead is easy to calculate. For MTBDL, there are various of
documents online, for example:

https://jontse.com/courses/files/cornell/ece5730/Lecture24.pdf

For your questions:

> a) recommended number of disks included in RAID array set?
I would personally recommend 12 to 15 HDDs per array.

> b) Is it possible to include all 84 disks in one array and leave 2 of
them as host spare?
It is possible, but not recommended. 84 disks per array really hurts
reliability.

> c) Is there a raid6 best practices document to refer to ?
I am not aware of such documents.

Hope these help.

Song

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: mdadm - raid6 best practices ?
  2017-09-22 18:26 ` Song Liu
@ 2017-09-22 19:24   ` Wols Lists
  2017-09-22 21:44     ` John Stoffel
  0 siblings, 1 reply; 6+ messages in thread
From: Wols Lists @ 2017-09-22 19:24 UTC (permalink / raw)
  To: linux-raid; +Cc: nkshirsa

On 22/09/17 19:26, Song Liu wrote:
> I would say this is a tradeoff between space overhead (2 parity disks per
> array) and data reliability (mean time before data loss, MTBDL, or MTTF).
> Space overhead is easy to calculate. For MTBDL, there are various of
> documents online, for example:
> 
> https://jontse.com/courses/files/cornell/ece5730/Lecture24.pdf
> 
> For your questions:
> 
>> a) recommended number of disks included in RAID array set?
> I would personally recommend 12 to 15 HDDs per array.
> 
My gut feel too was that 84 is an awful lot of disks ...

>> b) Is it possible to include all 84 disks in one array and leave 2 of
> them as host spare?

Do you mean hot spare, or were you thinking of raid-6's two parity disks?

The problem with a hot spare is exactly that - when the array is powered
up, they will be powered up. Yes, with an array that size I guess you
really do want a bunch of hot spares configured, but I'm not sure that's
really a good use of disks. If your main disks are beginning to die, the
spares could easily be going the same way :-(

> It is possible, but not recommended. 84 disks per array really hurts
> reliability.
> 
>> c) Is there a raid6 best practices document to refer to ?

> I am not aware of such documents.
> 
I don't know as it's really a "best practices" document, but there's a
fair bit in the archaeology section of the website you might find
interesting. More about optimisation and speed tests and stuff, but
because it was all old when we started updating the site last year,
that's why it ended up in archaeology.

One thing you really must do is regular scrubs. And MAKE SURE that you
have lots of active and passive monitoring - it would be oh so easy to
lose three disks the moment the guy on watch gets casual and stops
checking ... I don't have access to the stats off the top of my head,
but with that many disks, losing a couple a month to failures doesn't
seem that far-fetched.

> Hope these help.
> 
If you do come across some stuff (or write it yourself :-) please let me
know - this is exactly the stuff that should be on the website if I can
find it.

> Song

Cheers,
Wol

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: mdadm - raid6 best practices ?
  2017-09-22 19:24   ` Wols Lists
@ 2017-09-22 21:44     ` John Stoffel
  0 siblings, 0 replies; 6+ messages in thread
From: John Stoffel @ 2017-09-22 21:44 UTC (permalink / raw)
  To: Wols Lists; +Cc: linux-raid, nkshirsa

>>>>> "Wols" == Wols Lists <antlists@youngman.org.uk> writes:

Wols> On 22/09/17 19:26, Song Liu wrote:
>> I would say this is a tradeoff between space overhead (2 parity disks per
>> array) and data reliability (mean time before data loss, MTBDL, or MTTF).
>> Space overhead is easy to calculate. For MTBDL, there are various of
>> documents online, for example:
>> 
>> https://jontse.com/courses/files/cornell/ece5730/Lecture24.pdf
>> 
>> For your questions:
>> 
>>> a) recommended number of disks included in RAID array set?
>> I would personally recommend 12 to 15 HDDs per array.
>> 
Wols> My gut feel too was that 84 is an awful lot of disks ...

It really is... just do the math.  If you have 84 disks, and two of
them are parity, what's the rate of failures that gives you three disk
failures and them *boom* your data is gone.

Also, with that wide a stripe, you then have *horrible* performance
when you update a small 32k file, it has to read and re-write 81 disks
worth of data.  You're going to have horrible performance.

It would be smarter to have 12-16 disks in RAID6 pairs, then you could
either stripe or append to them.  I'd probably not even do that unless
I needed a single large volume.  The goal is to minimize data loss if
something goes wrong.

You also don't mention what filesystem(s) you've looked into for
this.  Or how you plan of sharing this disk space to other systems.
This is another area you need to be careful off.

Also, when you have this many disks in your system, which sounds like
one of the backblaze.com systems, you need to think about your
controllers and whether or not you're using expanders, etc.

If you're just going to maximum space for the least money, you could
just go with RAID0 and stripe data across the disks.  Pretty fast I
bet, but if you lose one... boom!  All gone.

You could do five 16 disk RAID6 arrays, leaving you with four hot
spares.  Then I'd probably just make them all seperate XFS
filesystems, especially since I don't know if you're using 4Tb disks
or some other size.

When you have this much space... it pays to be cautious, because users
will assume it's reliable and won't lose their data.

John

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: mdadm - raid6 best practices ?
  2017-09-22  3:55 mdadm - raid6 best practices ? Nikhil Kshirsagar
  2017-09-22 18:26 ` Song Liu
@ 2017-09-23  0:40 ` Stan Hoeppner
  2017-09-23  3:22   ` Nikhil Kshirsagar
  1 sibling, 1 reply; 6+ messages in thread
From: Stan Hoeppner @ 2017-09-23  0:40 UTC (permalink / raw)
  To: Nikhil Kshirsagar, Linux RAID

On 09/21/2017 10:55 PM, Nikhil Kshirsagar wrote:
> Hello linux-raid,
>
> A customer has some questions about raid6 best practices. They are
> using a 84-disk MD1280 Expansion Shelf (seagate disks). They want to
> use mdadm to setup a s/w raid, using raid6.
>
> The questions are
>
> a) recommended number of disks included in RAID array set?
> b) Is it possible to include all 84 disks in one array and leave 2 of
> them as host spare?
> c) Is there a raid6 best practices document to refer to ?
>
> Can anyone point me to me any internal docs or articles to construct a
> reply to the customer?
>
> Thanks,
> Nikhil.

The single most important question:

What is the workload?

Start the discussion there, or everything else is meaningless.

--
Stan

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: mdadm - raid6 best practices ?
  2017-09-23  0:40 ` Stan Hoeppner
@ 2017-09-23  3:22   ` Nikhil Kshirsagar
  0 siblings, 0 replies; 6+ messages in thread
From: Nikhil Kshirsagar @ 2017-09-23  3:22 UTC (permalink / raw)
  To: Stan Hoeppner; +Cc: Linux RAID

Thank you all for the information, I'll get some more workload
details. Thanks again!

-nikhil.

On Sat, Sep 23, 2017 at 6:10 AM, Stan Hoeppner <stan@hardwarefreak.org> wrote:
> On 09/21/2017 10:55 PM, Nikhil Kshirsagar wrote:
>>
>> Hello linux-raid,
>>
>> A customer has some questions about raid6 best practices. They are
>> using a 84-disk MD1280 Expansion Shelf (seagate disks). They want to
>> use mdadm to setup a s/w raid, using raid6.
>>
>> The questions are
>>
>> a) recommended number of disks included in RAID array set?
>> b) Is it possible to include all 84 disks in one array and leave 2 of
>> them as host spare?
>> c) Is there a raid6 best practices document to refer to ?
>>
>> Can anyone point me to me any internal docs or articles to construct a
>> reply to the customer?
>>
>> Thanks,
>> Nikhil.
>
>
> The single most important question:
>
> What is the workload?
>
> Start the discussion there, or everything else is meaningless.
>
> --
> Stan

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2017-09-23  3:22 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-22  3:55 mdadm - raid6 best practices ? Nikhil Kshirsagar
2017-09-22 18:26 ` Song Liu
2017-09-22 19:24   ` Wols Lists
2017-09-22 21:44     ` John Stoffel
2017-09-23  0:40 ` Stan Hoeppner
2017-09-23  3:22   ` Nikhil Kshirsagar

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).