From: David Greaves <david@dgreaves.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Swapping out for larger disks
Date: Tue, 08 May 2007 12:35:47 +0100 [thread overview]
Message-ID: <46406093.2080205@dgreaves.com> (raw)
In-Reply-To: <464055F5.2090108@wasp.net.au>
Brad Campbell wrote:
> G'day all,
>
> I've got 3 arrays here. A 3 drive raid-5, a 10 drive raid-5 and a 15
> drive raid-6. They are all currently 250GB SATA drives.
>
> I'm contemplating an upgrade to 500GB drives on one or more of the
> arrays and wondering the best way to do the physical swap.
>
> The slow and steady way would be to degrade the array, remove a disk,
> add the new disk, lather, rinse, repeat. After which I could use mdadm
> --grow. There is the concern of a degraded array here though (and one of
> the reasons I'm looking to swap is some of the disks have about 30,000
> hours on the clock and are growing the odd defect).
Assuming hotswap and for maximum uptime/minimal exposure to risk... a while back
there was a discussion of a fiddly way that involved adding a disk, making a
mirror, removing the old disk, breaking the mirror. ( See archive for details)
>
> I was more wondering about the feasibility of using dd to copy the drive
> contents to the larger drives (then I could do 5 at a time) and working
> it from there.
Err, if you can dd the drives, why can't you create a new array and use xfsdump
or equivalent? Is downtime due to copying that bad?
David
next prev parent reply other threads:[~2007-05-08 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 10:50 Swapping out for larger disks Brad Campbell
2007-05-08 11:28 ` Michael Tokarev
2007-05-08 11:35 ` David Greaves [this message]
2007-05-08 12:43 ` Brad Campbell
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=46406093.2080205@dgreaves.com \
--to=david@dgreaves.com \
--cc=brad@wasp.net.au \
--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;
as well as URLs for NNTP newsgroup(s).