From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] GUI front-end for LVM
Date: Wed, 25 Jul 2001 21:33:00 +0200 [thread overview]
Message-ID: <20010725213300.A27765@sistina.com> (raw)
In-Reply-To: <20010725144221.D30937@linux.com>; from tack@linux.com on Wed, Jul 25, 2001 at 02:42:21PM -0400
On Wed, Jul 25, 2001 at 02:42:21PM -0400, Jason Tackaberry wrote:
> * Gonyou, Austin (austin@coremetrics.com) [010725 14:39]:
> > I agree....but this would have to be something like what I was talking
> > about earlier with what I thought that LVM should be able to do
> > eventually. Dynamic reallocation/re-striping at any raid level.
>
> The impression I got from the LVM FAQ was that LVM will not support
> RAID1 basically because md does.
And not just RAID1.
Yes, the idea is to combine existing modular feature sets like LVM/MD.
With the enhancent stacking support in 2.4 the user has all the flexibility
to stack LVM on top of MD or vice versa.
> Maybe Heinz can shed some light on
> that situation and about the dynamic reallocation/restriping issue?
LVM just supports RAID0 to offer performance.
Constraint in the actual allocator is, that you can't extend a stripe beyond
a PV :-(
We want to remove that constraint in post 1.0 LVM.
If that's done, users can add additional PVs (which can be based on
SW/HW RAID1/5/whatever) and extend RAID0 LVs onto those.
Until then, one can stripe over multiple LVs using MD. Those LVs can be
resized equally in order to resize the striped MD. Care needs to be taken,
that the LVs are allocated/extended on distinct PVs.
>
> Jason.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-07-25 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 18:34 [linux-lvm] GUI front-end for LVM Gonyou, Austin
2001-07-25 18:42 ` Jason Tackaberry
2001-07-25 19:33 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-25 17:48 Gonyou, Austin
2001-07-25 17:44 Jason Tackaberry
2001-07-25 17:47 ` Patrick Boutilier
2001-07-25 18:29 ` Jason Tackaberry
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=20010725213300.A27765@sistina.com \
--to=mauelshagen@sistina.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