From: Ian Pilcher <arequipeno@gmail.com>
To: linux-raid@vger.kernel.org
Subject: RAID types & chunks sizes for new NAS drives
Date: Sun, 21 Jun 2020 11:23:35 -0500 [thread overview]
Message-ID: <rco1i8$1l34$1@ciao.gmane.io> (raw)
I'm replacing the drives in my 5-bay NAS, and planning how I'm going to
divide them up. My general plan is to create a matching set of
partitions on the drives, and then create RAID devices across the sets
of partitions, for example:
md1: /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
md2: /dev/sdb2 /dev/sdc2 /dev/sdd2 /dev/sde2 /dev/sdf2
⋮ ⋮ ⋮ ⋮ ⋮ ⋮
md16: /dev/sdb16 /dev/sdc16 /dev/sdd16 /dev/sde16 /dev/sdf16
This will give me the flexibility to create RAID devices of different
types, as well as maybe(?) reducing the "blast radius" if a particular
portion of a disk goes bad.
I believe that it makes sense to use at least 2 different RAID levels -
RAID-10 for "general" use and RAID-6 for media content. Does this make
sense?
If so, does anyone have any thoughts or pointers on the chunk size,
particularly for RAID-10? (I assume that RAID-6 will have similar
considerations to RAID-5, and so a large chunk size would make sense,
particularly for large media files.)
Any other thoughts?
Thanks!
--
========================================================================
In Soviet Russia, Google searches you!
========================================================================
next reply other threads:[~2020-06-21 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 16:23 Ian Pilcher [this message]
2020-06-23 1:45 ` RAID types & chunks sizes for new NAS drives John Stoffel
2020-06-23 2:31 ` o1bigtenor
2020-06-23 17:01 ` John Stoffel
2020-06-24 22:13 ` o1bigtenor
2020-06-23 12:26 ` Nix
2020-06-23 18:50 ` John Stoffel
2020-06-23 15:36 ` antlists
2020-06-23 18:55 ` John Stoffel
2020-06-24 12:32 ` Phil Turmel
2020-06-24 14:49 ` John Stoffel
2020-06-24 18:41 ` Wols Lists
2020-06-23 20:27 ` Ian Pilcher
2020-06-23 21:30 ` John Stoffel
2020-06-23 23:16 ` Ian Pilcher
2020-06-24 0:34 ` John Stoffel
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='rco1i8$1l34$1@ciao.gmane.io' \
--to=arequipeno@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox