linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gordon Mohr <gojomo@bitzi.com>
To: linux-raid@vger.kernel.org
Subject: Re: Shrinking on-disk size of RAID1 array?
Date: Fri, 30 Sep 2005 11:37:21 -0700	[thread overview]
Message-ID: <433D85E1.5030708@bitzi.com> (raw)
In-Reply-To: <63d08afd0509300232u36141930h@mail.gmail.com>

Matthew Coulson wrote:
>>I'm hoping to shrink the per-component size of an active RAID1
>>array, so that I can transition the array to a smaller, faster
>>set of drives.
> 
> 
> I may be missing something here, but why not connect up the new
> drives, setup the arrays, simply cp -R * everything over to the new
> filesystems and update fstab and mdadm.conf? I can understand wanting
> to let the system handle it all for you, but this way you'll get a
> free defrag to boot :)

Largest reason is that I want to minimize system downtime. My
working assumption is that the 'parted' resize and 'mdadm'
grow (shrink) would take minutes (or tens of minutes), then
the background sync to the new smaller drive could happen
at a leisurely pace, while services which actively write to
the array remain up.

I would expect a plain 'cp -R' to take hours, during
which (to be safe) all services using the array should be
stopped. (Perhaps I could do an initial 'cp -R' while services
are running, then a quicker rsync for consistency when services
are down?)

If my assumption about the relative time required of 'parted'
resize and 'mdadm' grow is wrong, the simple copy approach
would be more attractive.

- Gordon

      reply	other threads:[~2005-09-30 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30  6:02 Shrinking on-disk size of RAID1 array? Gordon Mohr (@ Bitzi)
2005-09-30  9:32 ` Matthew Coulson
2005-09-30 18:37   ` Gordon Mohr [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=433D85E1.5030708@bitzi.com \
    --to=gojomo@bitzi.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).