From: Andreas Dilger <adilger@turbolinux.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Roger Abrahamsson <hyperion@gnyrf.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: resizing of raid5?
Date: Wed, 1 Aug 2001 11:56:56 -0600 (MDT) [thread overview]
Message-ID: <200108011756.f71HuuL2006872@webber.adilger.int> (raw)
In-Reply-To: <15207.63232.611617.37794@notabene.cse.unsw.edu.au> "from Neil Brown at Aug 1, 2001 10:33:04 pm"
Neil Brown writes:
> On Wednesday August 1, hyperion@gnyrf.net wrote:
> > Just figured if anyone could give some information about resizing of
> > software raid5 systems (2.4.x kernels)? I've been looking all over for
> > information about if this is possible or not currently, and if not, how
> > this system of raid cluster blocks work in conjunction with ext2.
>
> The only way to resize a raid5 array is to back up, rebuild, and
> re-load. Any attempt to re-organise the data, or the linkage, to
> avoid this would be more trouble that it is worth.
Hmm, this surprises me. I would have thought it possible to do
"resizing" at least by adding new stripes to the end of the current
RAID 5 volume, using N+1 new "disks" to make up a new stripe group.
Adding a new disk into the stripe set and re-striping the whole thing
is definitely a lot harder.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-08-01 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 9:25 Roger Abrahamsson
2001-08-01 12:33 ` Neil Brown
2001-08-01 14:59 ` Jakob Østergaard
2001-08-01 16:57 ` Roger Abrahamsson
2001-08-02 5:52 ` Neil Brown
2001-08-02 11:33 ` Roger Abrahamsson
2001-08-01 17:56 ` Andreas Dilger [this message]
2001-08-02 6:04 ` Neil Brown
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=200108011756.f71HuuL2006872@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=hyperion@gnyrf.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®