[linux-lvm] lvm/fs issue
david.rosenstrauch at csfb.com
Tue Dec 21 17:22:23 UTC 2004
> -----Original Message-----
> From: linux-lvm-bounces at redhat.com
> [mailto:linux-lvm-bounces at redhat.com]On Behalf Of Kevin P. Fleming
> Sent: Tuesday, December 21, 2004 12:11 PM
> To: LVM general discussion and development
> Subject: Re: [linux-lvm] lvm/fs issue
> Rosenstrauch, David wrote:
> > Although I currently have only 1 logical volume, and all my
> PV's are currently
> > a part of it, that's not necessarily how things will always be. I
> > intentionally partitioned most of my disk into ~2GB chunks
> like this, so that
> > I can have a pool of 2GB PV's which I can throw at
> whichever LV needs it, and
> > thereby rid myself of future space constraint issues I've
> run into in the past
> > with traditional partitioning.
> But that's the whole point of LVM in the first place!
> If you make a single PV, with a VG including it, you can
> carve it up and
> re-carve it up however you like, for whatever LVs you have or
> create in
> the future. You can even _shrink_ LVs and make the space available to
> other LVs, which you cannot do with partitions.
Hmm. I guess I didn't quite understand that then. I knew that you could have
a LV that spans multiple PV's (which is what I figured was the whole point of
LVM - you could just keep throwing more PV's at an LV as your space needs
grew), but I didn't know that you could have a PV that gets split across
multiple LV's. I guess I just assumed (don't know why) that each PV had to be
dedicated to 1 and only 1 LV.
Thanks for setting me straight then. No real big problem for me the way I
have it now, though. I guess I might suffer a little bit performance-wise,
but this is my desktop development machine, not a server, so no huge loss.
Good to have my facts straight for the future, though.
This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.
More information about the linux-lvm