linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
	Stefan Neufeind <linux-raid@stefan-neufeind.de>,
	linux-raid@vger.kernel.org
Subject: Re: Extendable raid - with soft-raid 5 and new mdadm?
Date: Mon, 01 Nov 2004 17:28:16 -0800	[thread overview]
Message-ID: <4186E2B0.6090105@h3c.com> (raw)
In-Reply-To: <1099356271.30526.100.camel@compaq-rhel4.xsintricity.com>


I also had success with raidreconfig and raid5, although I had a failure 
too. I was testing it to see if a strategy of adding disks as I needed 
them would work, and I discovered that it is *very* *very* touchy about 
the size of the partitions.

Where mdadm will just use the smallest partition as the limit for all 
units in the array, raidreconfig had an error related to partition sizes 
at the very end of its attempt to grow the array.

When I made the partition sizes the exact same block size it worked 
flawlessly, though slowly, in two separate tests, one going from 2x250GB 
to 3x250, and another going from 3x250 to 4x250.

I intend to use it to grow the array semi-indefintely, but I also have 
thorough, automatic backups so I may be more cavalier than people who 
care more about a specific instance of the data.

-Mike

Doug Ledford wrote:
> On Mon, 2004-11-01 at 12:11 +1100, Neil Brown wrote:
> 
> 
>>There is a program called "raidreconfig" (I think) which can do this
>>off-line.   This is information only, not a recommendation as I have
>>never used it or looked at it.
> 
> 
> I've used it once.  It worked, it grew my raid5 array for me.  Took
> forever, but it worked.
> 


      reply	other threads:[~2004-11-02  1:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31 18:30 Extendable raid - with soft-raid 5 and new mdadm? Stefan Neufeind
2004-11-01  1:11 ` Neil Brown
2004-11-02  0:44   ` Doug Ledford
2004-11-02  1:28     ` Mike Hardy [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=4186E2B0.6090105@h3c.com \
    --to=mhardy@h3c.com \
    --cc=dledford@redhat.com \
    --cc=linux-raid@stefan-neufeind.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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).