From: Brad Campbell <brad@wasp.net.au>
To: David Greaves <david@dgreaves.com>
Cc: RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: Swapping out for larger disks
Date: Tue, 08 May 2007 16:43:02 +0400 [thread overview]
Message-ID: <46407056.8000607@wasp.net.au> (raw)
In-Reply-To: <46406093.2080205@dgreaves.com>
David Greaves wrote:
>> 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?
I can only do 5 at a time. (10 slots, 5 source - 5 destination).
I'm not worried about the downtime so much as the constant swapping of disks. This way I can do it
in 2 or 3 blocks at most.
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
prev parent reply other threads:[~2007-05-08 12:43 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
2007-05-08 12:43 ` Brad Campbell [this message]
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=46407056.8000607@wasp.net.au \
--to=brad@wasp.net.au \
--cc=david@dgreaves.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;
as well as URLs for NNTP newsgroup(s).