linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Growing after replacing with larger discs
Date: Sat, 13 Mar 2010 18:13:20 +0000	[thread overview]
Message-ID: <4B9BD5C0.2050902@anonymous.org.uk> (raw)
In-Reply-To: <70ed7c3e1003130721u29cf938ep9313a10078ee5e52@mail.gmail.com>

On 13/03/2010 15:21, Majed B. wrote:
> You should never degrade the array to copy its contents. Its very
> risky. There might be bad sectors on one or more disks and if you
> don't have all disks at hand, you may not be able to rebuild the array
> on the new disk.

OK that's fair, you're right I don't want to risk losing data because I 
was using a degraded array.

> As for using dd, as others have pointed, the metadata won't be in
> place and if you create a new array after using dd, it'll still
> require a resync and the data will be destroyed.

I don't see whay either it'd require a resync - although I didn't say 
it, I was planning to zero the rest of the larger drives and recreate 
with --assume-clean - nor why data would be destroyed if I didn't create 
with --assume-clean, after all the data will all be in the right place.

But I think on balance I'm going to save the contents of the original 
array to an extra drive, create a new array on the big discs, and copy 
the data back. It shouldn't take too much more time than copying the 
discs individually with dd, even though I'm copying the data twice 
rather than once, and it's both safer and gives me a free defrag.

Cheers,

John.

  reply	other threads:[~2010-03-13 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.
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 [this message]
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=4B9BD5C0.2050902@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --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).