From: "Majed B." <majedb@gmail.com>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Growing after replacing with larger discs
Date: Fri, 12 Mar 2010 21:13:07 +0300 [thread overview]
Message-ID: <70ed7c3e1003121013u6dc745abhe1376b28f01e68ec@mail.gmail.com> (raw)
In-Reply-To: <4B9A8225.3010805@anonymous.org.uk>
If you do this kind of thing a lot, or often enough, then it's better
to get a portable NAS, copy filesystem contents to it, then dump the
stuff back.
You can save yourself time with the new arrays by zeroing all the new
disks, and then when creating the new array, use assume-clean. That'll
prevent the array from resyncing, and you'll get full speed when
copying the filesystem contents back to the new array.
dd allows parallel writing to output devices.
On Fri, Mar 12, 2010 at 9:04 PM, John Robinson
<john.robinson@anonymous.org.uk> wrote:
> On 12/03/2010 18:00, Majed B. wrote:
>>
>> I'm not sure if it is going to work or not, what you suggested.
>>
>> But if you can run all disks at the same time, then why not create a
>> new array and copy the files over?
>
> I can't, I only have the 3 drive caddies, so I was going to shut down, start
> up from a CD, copy each drive individually, then put the 3 larger drives in
> all at once.
>
> Cheers,
>
> John.
>
>
--
Majed B.
next prev parent reply other threads:[~2010-03-12 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 17:39 Growing after replacing with larger discs John Robinson
2010-03-12 18:00 ` Majed B.
2010-03-12 18:04 ` John Robinson
2010-03-12 18:13 ` Majed B. [this message]
2010-03-12 18:09 ` Luca Berra
2010-03-13 15:18 ` John Robinson
2010-03-13 15:21 ` Majed B.
2010-03-13 18:13 ` John Robinson
2010-03-13 18:22 ` Majed B.
2010-03-15 15:17 ` Stefan /*St0fF*/ Hübner
[not found] ` <aebf5d971003131242q234a6c5ct441dd995a9c6a541@mail.gmail.com>
2010-03-13 20:45 ` Beolach
2010-03-13 21:00 ` Majed B.
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=70ed7c3e1003121013u6dc745abhe1376b28f01e68ec@mail.gmail.com \
--to=majedb@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;
as well as URLs for NNTP newsgroup(s).