public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: David T-G <davidtg-robot@justpickone.org>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: growing a RAID5 array by adding disks later
Date: Thu, 28 Oct 2021 13:36:27 +0000	[thread overview]
Message-ID: <20211028133626.GX6557@justpickone.org> (raw)

Hi, all --

It's time to replace a few 4T disks in our little server.  I don't
particularly want to go back with more 4T disks (although the same
model sure are cheap these days! :-) and figure I should put in larger
drives as I go.  I am then left with weighing simple $/G vs total price;
bigger drives can be cheaper per volume but of course more overall.
My first approach is to put newer, larger drives in place and expect to
grow into the empty space when all of the old ones have been swapped out.

But ...  If I were to splurge and buy 3ea big drives to replace all of
the space that I have now, how practical is it to grow that RAID5 array
by adding additional drives later?  My eventual goal would be to get
to 8-10 devices in a RAID6 layout (two "extras"), but of course I can't
afford that today.  Do I have an easy path to get there in the long run?

[BTW, can I convert an array from RAID5 to RAID6, too?]

On the other hand, I do have the empty slots (currently filled with
scratch drives here and there), so I could both replace my aging drives
and add more and just grow this array 1) if the growth idea is practical
and 2) if I don't get to splurge.


TIA

:-D
-- 
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt


             reply	other threads:[~2021-10-28 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 13:36 David T-G [this message]
2021-10-28 14:05 ` growing a RAID5 array by adding disks later John Atkins
2021-10-28 16:42 ` Wol
2021-10-28 19:11   ` Roger Heflin

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=20211028133626.GX6557@justpickone.org \
    --to=davidtg-robot@justpickone.org \
    --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