linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent CARON <lcaron@apartia.fr>
To: Linux <linux-raid@vger.kernel.org>
Subject: Expanding array by changing disks (one by one)
Date: Thu, 14 Apr 2005 12:11:20 +0200	[thread overview]
Message-ID: <425E41C8.7050704@apartia.fr> (raw)

Hello,

We are in the process of increasing the size our RAID Arrays as our 
storage needs increase.

I've got 2 solutions for this:

- Copy the data over a new array and replace the disks

- Replace each disk (one after the other(after resync)) of the existing 
array with a bigger one.

Start:
    - Array is ok
- Remove 1 disk
    - Array is degraded
- Add a bigger disk
    - Resync
- Remove another disk
    - Array is degraded
- Add a bigger disk
    - Resync
.....

Would this be the 'state of the art' way ?

Will the filesystem cope with it?

Is my mind completely broken?

Thanks for your help.

Laurent



             reply	other threads:[~2005-04-14 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 10:11 Laurent CARON [this message]
2005-04-14 10:15 ` Expanding array by changing disks (one by one) Andy Smith
2005-04-14 11:02 ` Gordon Henderson
2005-04-14 15:08   ` Mike Hardy
2005-04-14 11:04 ` David Greaves

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=425E41C8.7050704@apartia.fr \
    --to=lcaron@apartia.fr \
    --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).