From: Roger Abrahamsson <hyperion@gnyrf.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: resizing of raid5?
Date: Wed, 01 Aug 2001 18:57:01 +0200 (CEST) [thread overview]
Message-ID: <996685021.3b6834dd0829d@stargate.gnyrf.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>
Quoting Neil Brown <neilb@cse.unsw.edu.au>:
>
> 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.
>
> NeilBrown
Well, the problem is that it's not that easy when you want to backup say 200GB
of data to find anyone that can hold it for the day while you do it. Well, at
least do it without charge :)
Having things offline for up to a few days while you do the rebuild is okay for
my case, but the offloading the data is not. If I have understood md and raid5,
you create blocks of a fixed size, and calculate the checksum on each "stripe".
To rebuild this looks a bit like disk defragmentation to me, or am I totally
wrong here?
next prev parent reply other threads:[~2001-08-01 15:00 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 [this message]
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=996685021.3b6834dd0829d@stargate.gnyrf.net \
--to=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®