From: lembark@wrkhors.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] RAID extension and lvm
Date: Sun Jul 14 11:27:01 2002 [thread overview]
Message-ID: <15050000.1026663876@duke> (raw)
In-Reply-To: <Pine.LNX.4.44.0207141635090.22457-100000@poseidon.ihs.uni-stuttgart.de>
> Sorry, but there is no pvresize command.
You wouldn't want it anyway.
There isn't any way to "resize" an fault-tolerant RAID
system (1/3/5) and you can get more flexable, reliable
results with LVM than RAID0 anyway.
The way to add space into a VG is by incorporating new
PV's with vgextend. If you want to grow a fault-tolerant
system then build new RAID5 groups and add them as new
PV's.
--
Steven Lembark 2930 W. Palmer
Workhorse Computing Chicago, IL 60647
+1 800 762 1582
next prev parent reply other threads:[~2002-07-14 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 9:17 [linux-lvm] RAID extension and lvm Ralf Eisinger
2002-07-12 9:27 ` Goetz Bock
2002-07-14 9:40 ` Ralf Eisinger
2002-07-14 9:55 ` Goetz Bock
2002-07-14 11:27 ` lembark [this message]
2002-07-14 12:41 ` Ralf Eisinger
2002-07-14 12:47 ` Tim
2002-07-14 13:20 ` Ralf Eisinger
2002-07-14 13:45 ` Kirby C. Bohling
2002-07-14 14:14 ` Christian Limpach
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=15050000.1026663876@duke \
--to=lembark@wrkhors.com \
--cc=linux-lvm@sistina.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