Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Jon Hardcastle <jd_hardcastle@yahoo.com>
To: Jon@ehardcastle.com, Felipe Alvarez <felipe.alvarez@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Fwd: Majordomo results: Re: Majordomo results: .
Date: Wed, 24 Feb 2010 01:50:28 -0800 (PST)	[thread overview]
Message-ID: <394052.48164.qm@web51305.mail.re2.yahoo.com> (raw)
In-Reply-To: <e4ae6451002240145i704454cdt94435913054c6122@mail.gmail.com>

--- On Wed, 24/2/10, Felipe Alvarez <felipe.alvarez@gmail.com> wrote:

> From: Felipe Alvarez <felipe.alvarez@gmail.com>
> Subject: Re: Fwd: Majordomo results: Re: Majordomo results: .
> To: Jon@ehardcastle.com
> Cc: linux-raid@vger.kernel.org
> Date: Wednesday, 24 February, 2010, 9:45
> > The beauty of that being that
> when all the drives
> > have been retired/failed and the smallest partition
> > size is now 500GB or whatever you can
> > --grow=max and get that unused space.
> >
> Thanks. That's a good idea, because I would eventually like
> to make
> the array larger than it is as the drives get replaced, one
> at a time.
> Would the command be:
> $ mdadm --grow /dev/md0 --size=max DEVICE1 DEVICE2 DEVICE3
> DEVICE4
> 
> Felipe
> --

Think it is simply mdadm --grow /dev/md0 --size=max 

But speaking from experience you'll likely run out of space before the bitter pill of retiring the drives/being unlucky enough for them to fail happens. You'll be adding new drives before you know it! And then... you'll probably want to consider RAID6 once you go over ~1TB per drive.



      

      reply	other threads:[~2010-02-24  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1753924Ab0BXIaN/20100224083013Z+196@vger.kernel.org>
     [not found] ` <e4ae6451002240032q17390a5ci4baa86cc7be8270e@mail.gmail.com>
     [not found]   ` <e4ae6451002240048w7822735dx6143c07274fe99d5@mail.gmail.com>
2010-02-24  8:54     ` Fwd: Majordomo results: Re: Majordomo results: Felipe Alvarez
2010-02-24  9:07       ` Jon Hardcastle
2010-02-24  9:45         ` Felipe Alvarez
2010-02-24  9:50           ` Jon Hardcastle [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=394052.48164.qm@web51305.mail.re2.yahoo.com \
    --to=jd_hardcastle@yahoo.com \
    --cc=Jon@ehardcastle.com \
    --cc=felipe.alvarez@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