From: Neil Brown <neilb@suse.de>
To: "Patrick J. LoPresti" <lopresti@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Resize RAID-0?
Date: Sat, 13 Mar 2010 11:50:02 +1100 [thread overview]
Message-ID: <20100313115002.3f085832@notabene.brown> (raw)
In-Reply-To: <23986fd91003121609o19b9fd6s22e3711c9d9c8455@mail.gmail.com>
On Fri, 12 Mar 2010 16:09:43 -0800
"Patrick J. LoPresti" <lopresti@gmail.com> wrote:
> Addendum (for the archives).
>
> EVMS claims to support this:
>
> http://evms.sourceforge.net/user_guide/#resizeraid0
Just for clarification, that is an off-line non-interruptible (better have a
UPS) resize.
There is a command line tool to do this:
http://unthought.net/raidreconf/
however I wouldn't recommend it, because if anything goes wrong in the middle,
you lose your data.
NeilBrown
prev parent reply other threads:[~2010-03-13 0:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 3:39 Resize RAID-0? Patrick J. LoPresti
2010-03-12 5:17 ` Michael Evans
2010-03-12 10:40 ` John Robinson
2010-03-12 11:53 ` Neil Brown
2010-03-12 11:36 ` Kristleifur Daðason
2010-03-12 17:03 ` Patrick J. LoPresti
2010-03-13 0:09 ` Patrick J. LoPresti
2010-03-13 0:50 ` Neil Brown [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=20100313115002.3f085832@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lopresti@gmail.com \
/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).