From: "Michał Sawicz" <michal@sawicz.net>
To: David Brown <david@westcontrol.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Best strategy to incrementally replace smaller HDDs
Date: Fri, 09 Sep 2011 16:12:36 +0200 [thread overview]
Message-ID: <1315577572.14468.11.camel@michal-laptop> (raw)
In-Reply-To: <j4d19g$1r4$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2630 bytes --]
Dnia 2011-09-09, pią o godzinie 14:34 +0200, David Brown pisze:
> On 09/09/2011 12:48, Michał Sawicz wrote:
> > Hi all, given the configuration below:
> > * 8 x 1TB HDDs
> > * 2 x 2TB HDDs
> >
> > On which I currently have:
> > * (10 x 1TB) RAID6 - persistent storage
> > * (2 x 1TB) system / temporary storage etc.
> >
>
> By this do you mean that you have 8 x 1TB drives with a 1 TB partition
> on each, and 2 x 2T drives with 2 x 1TB partition on each? So that the
> two big disks are shared with both raids?
Yes, that wasn't like that before, but that's a result of exchanging two
1TB drives to 2TB ones.
> > I want to replace the 1TB drives for 2TB ones on an as-needed basis,
> > what strategy would you recommend?
>
> This sounds like you are thinking that you can replace a single disk in
> your RAID6 array and get more storage - changing 10 x 1 TB raid6 = 8TB
> into 9 x 1TB + 1 x 2TB raid6 = 9 TB. It doesn't work like that. You
> will have to replace /all/ your 1 TB devices with 2 TB devices (and move
> the second raid off the two existing 2TB devices) - all members of the
> raid6 must be the same size.
Actually no, I know how RAIDs work, so the three schemes I described
below account for that.
> To help you plan your upgrades, it is also useful to know your
> partitioning scheme (for example, do you use LVM?), whether you have the
> space to put lots more drives in the system or must do it one drive at a
> time, whether you can take the system off-line during the process, and
> whether you need to do the upgrade quickly or can spend a week or so at
> it (some of these are conflicting requirements).
No LVM here. The most important - big RAID6 - is a single partition. The
remaining 2 x 1TB on the big drives are split into RAID1 for boot,
RAID10 for root, RAID0 for temporary storage and swap space. I can
temporarily put more drives in there. I can take it off-line for some
periods and I can do the upgrade over an extended period of time.
> Before you think about upgrading, however, make sure you have a solid
> backup. Then make sure you have a backup of that backup - and a plan
> for how to restore everything if something goes horribly wrong.
Yeah... I plan to rely on RAID's redundancy by moving data around,
growing / shrinking the filesystems and then shuffling the HDDs. I know
that's asking for trouble, but I haven't yet found a place to rent 8TBs
of storage for a week... And that's worked for me in the past, btw.
Twice, even, IIRC.
--
Michał (Saviq) Sawicz <michal@sawicz.net>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-09-09 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 10:48 Best strategy to incrementally replace smaller HDDs Michał Sawicz
2011-09-09 12:34 ` David Brown
2011-09-09 14:12 ` Michał Sawicz [this message]
2011-09-09 13:13 ` Robin Hill
2011-09-09 14:20 ` Michał Sawicz
2011-09-27 8:37 ` Best strategy to incrementally replace smaller HDDs [success story] Michał Sawicz
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=1315577572.14468.11.camel@michal-laptop \
--to=michal@sawicz.net \
--cc=david@westcontrol.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