linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Laurent CARON <lcaron@unix-scripts.info>
Cc: linux-raid@vger.kernel.org
Subject: Re: Growing a raid 6 array
Date: Thu, 1 Mar 2007 17:28:37 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703011728270.7560@p34.internal.lan> (raw)
In-Reply-To: <45E72549.2080108@unix-scripts.info>

You can only grow a RAID5 array in Linux as of 2.6.20 AFAIK.

Justin.

On Thu, 1 Mar 2007, Laurent CARON wrote:

> Hi,
>
> As our storage needs are growing i'm in the process of growing a 6TB
> array to 9TB by changing the disks one by one (500GB to 750GB).
>
> I'll have to partition the new drives with bigger partitions and then
> fail the array, remove a drive, add a new 750GB disk.... repeat it as
> long as 500GB disks are remaining in the system.
>
> The question now is to know if i'm right, or ... simply wrong in
> thinking that this operation is then just as simple as:
>
> server:~# mdadm -G /dev/mdX -n number_of_disks(same as original array)
>
> once done, i'll have to grow the filesystem (ext3) by issuing
>
> server:~# resize2fs -p /dev/mdX
>
>
>
> Does the fact that the ext3 partition is nearly full involves a bigger
> risk of screwing the data ?
>
> Would it be better/worse to have a bitmap (internal one) on the mdX
> device while growing it ?
>
> Thanks
>
> Laurent
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2007-03-01 22:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 19:11 Growing a raid 6 array Laurent CARON
2007-03-01 22:28 ` Justin Piszcz [this message]
2007-03-01 23:08   ` Laurent CARON
2007-03-01 23:14     ` Justin Piszcz
2007-03-02  1:59   ` Neil Brown
2007-03-02  9:51     ` Laurent CARON
2007-04-13  8:15     ` Laurent CARON
2007-04-13  8:27       ` Louis-David Mitterrand

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=Pine.LNX.4.64.0703011728270.7560@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=lcaron@unix-scripts.info \
    --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).