From: "Jakob Østergaard" <jakob@unthought.net>
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 16:59:07 +0200 [thread overview]
Message-ID: <20010801165907.A1293@unthought.net> (raw)
In-Reply-To: <996657922.3b67cb02ba717@stargate.gnyrf.net> <15207.63232.611617.37794@notabene.cse.unsw.edu.au>
In-Reply-To: <15207.63232.611617.37794@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Wed, Aug 01, 2001 at 10:33:04PM +1000
On Wed, Aug 01, 2001 at 10:33:04PM +1000, Neil Brown wrote:
> On Wednesday August 1, hyperion@gnyrf.net wrote:
> > Hello.
> >
> > 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 code is a bit tricky and not
> > too many comments to help one try and get a hold of how it works.
> > Any pointers for this would be nice.
>
> 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.
Well, yes and no.
I wrote a resizing tool for raid0 (this is code "A"). I later re-wrote that code
so that it could convert between raid-levels, and do resizing of those levels too
(this is code "B").
However, code "B" was never finished, it had some serious bugs. Code "A" has
been "mostly stable" (meaning, users and myself have resized several hundred
gigabytes of RAID-0, and I only know of one array that has been trashed).
Now, code "A" was shipped to one company - they re-wrote it to do RAID-5
resizing.
Code "B" was shipped to another company - they fixed the bugs.
Somewhere out there, there should be a tool that will do not only resizing of
the raid levels, but also conversion between them. It's GPL, it's based on my
code, but I haven't seen it yet :)
I have not had the changes back from any of those two companies - but this is
mainly because I've been too busy to care. They seem to intend to release the
changes (after all, my code was GPL), and I'm going to follow up on this when
I'm done with my thesis - which will be about in a month from now.
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2001-08-01 14:59 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 [this message]
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
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=20010801165907.A1293@unthought.net \
--to=jakob@unthought.net \
--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®