From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems and questions with LVM on a large raid system.
Date: Tue Mar 18 03:14:02 2003 [thread overview]
Message-ID: <20030318101206.D30525@sistina.com> (raw)
In-Reply-To: <20030315223607.GA16976@gw.silicide.dk>; from jon+lvm@silicide.dk on Sat, Mar 15, 2003 at 11:36:07PM +0100
On Sat, Mar 15, 2003 at 11:36:07PM +0100, jon+lvm@silicide.dk wrote:
> On Sat, Mar 15, 2003 at 01:59:59PM -0600, Steven Lembark wrote:
> >
> >
> > -- Jon Bendtsen <jon+lvm@silicide.dk>
> >
> > >>> that depends. You can stripe the lvm, but then you cant resize it.
> > >>> if you made a LV, then it would proberly just allokate all on one
> > >>> "disk", aka sda, and then on sdb.
> > >>
> > >> I'm using 100% of the VG for the same LV.
> > >>
> > >> I'm fine with not being able to resize it. Do I need the MD stuff to
> > >> stripe it?
> > >
> > >No. You can stripe using the LV system. But i would think that
> > >if you can shutdown the LV, then you might as well stop the VG,
> > >and do it on the raw device. (except this isnt as future proof
> > >as a LVM system is).
> >
> > Nor as flexable: with LVM you can easily grow the LV's, with
> > out LVM you are stuck with fixed partitions.
>
> that would be included in being future proof ;-D
> Besides, he wants to stripe it, and you cant extend a stripped
> LV (as far as i know).
Yes, you can.
Stripes are linited by the physical volume size in LVM1 though and the only way
to grow a striped LV there is to pvmove the stripe to a larger PV and extend
the LV afterwards.
LVM2 doesn't have such constraint any longer :)
>
>
>
> JonB
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
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:[~2003-03-18 3:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 13:53 [linux-lvm] Problems and questions with LVM on a large raid system Petro
2003-03-12 16:14 ` jon+lvm
2003-03-12 16:24 ` Kevin P. Fleming
2003-03-12 16:50 ` jon+lvm
2003-03-12 17:00 ` Kevin P. Fleming
2003-03-12 17:17 ` jon+lvm
2003-03-12 17:25 ` Kevin P. Fleming
2003-03-12 17:46 ` Petro
2003-03-13 2:44 ` Jon Bendtsen
2003-03-13 18:25 ` Petro
2003-03-14 2:32 ` Adrian Phillips
2003-03-15 13:50 ` Steven Lembark
2003-03-15 16:37 ` jon+lvm
2003-03-18 3:14 ` Heinz J . Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-12 21:03 Barry, Christopher
2003-03-13 2:45 ` Jon Bendtsen
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=20030318101206.D30525@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