From: Drew <drew.kay@gmail.com>
To: Lou Arnold <larnolda1@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Total free space using added VGs and LVs
Date: Mon, 19 Oct 2009 11:41:21 -0700 [thread overview]
Message-ID: <c268e4660910191141s5c5f3e1lf422c67f7f8bf423@mail.gmail.com> (raw)
In-Reply-To: <a5a956f70910191114r3025ec45r5ddb2e02620fb0c0@mail.gmail.com>
> But I thought that the purpose of LVM was to make a number of partitions
> look like one big one. So I can understand that with an added volume group,
> the filsesystems are separate, but for my (2) below, I expected all LVM-type
> partitions to seen as one large one.
The purpose of LVM is to make a bunch of physical drives look like one
big pool of storage space. A Volume Group is a container into which
you plug physical volumes (drives) so that the logical volumes can
allocate space from the pool (volume group) as needed.
> 1) Why would you want several logical volumes in one volume group?
The same reason(s) you would want to partition a regular hard drive.
Maybe you only want /home to have 20GB so your kids can't flood the
computer with downloaded music. Maybe you want /var/www to have
restricted permissions so your home web server is less vulnerable to
hackers. Maybe you're running a PVR application like MythTV and want a
high-performance filesystem like XFS for storing recorded shows.
All of these can be done with logical volumes, and are often easier under LVM.
> 2) Why would you want several volume groups at all?
You don't need multiple volume groups on a single machine. There are
certain uses though in which it is beneficial, usually in commercial
use.
--
Drew
"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
next prev parent reply other threads:[~2009-10-19 18:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 14:52 [linux-lvm] Total free space using added VGs and LVs Lou Arnold
2009-10-19 17:21 ` Stuart D. Gathman
2009-10-19 18:03 ` Drew
[not found] ` <a5a956f70910191114r3025ec45r5ddb2e02620fb0c0@mail.gmail.com>
2009-10-19 18:41 ` Drew [this message]
[not found] ` <a5a956f70910191200t340c02c2t28f14d3aef46cfdc@mail.gmail.com>
2009-10-19 19:51 ` Drew
2009-10-20 0:26 ` Lou Arnold
2009-10-20 3:19 ` Drew
[not found] ` <a5a956f70910201044j12e70c1cg78f454e580595815@mail.gmail.com>
2009-10-21 15:02 ` Lou Arnold
2009-10-21 15:28 ` Drew
2009-10-21 19:03 ` Lou Arnold
2009-10-21 19:18 ` Ryan Anderson
2009-10-23 0:26 ` Lou Arnold
2009-10-23 0:52 ` Stuart D. Gathman
2009-10-21 22:54 ` David
2009-10-23 6:52 ` Luca Berra
2009-10-23 19:06 ` Lou Arnold
2009-10-23 20:12 ` Ryan Anderson
2009-10-23 20:41 ` Lou Arnold
2009-10-24 0:06 ` Brian McCullough
2009-10-24 7:34 ` Luca Berra
2009-10-24 16:43 ` Lou Arnold
2009-10-24 17:04 ` brem belguebli
2009-10-24 19:16 ` Lou Arnold
2009-10-24 20:54 ` brem belguebli
2009-10-24 21:21 ` Lou Arnold
2009-10-24 22:04 ` Stuart D. Gathman
2009-10-25 8:46 ` Luca Berra
2009-10-25 13:13 ` Drew
2009-10-25 18:09 ` Stuart D. Gathman
2009-10-25 19:17 ` Stuart D. Gathman
2009-10-26 15:20 ` Lou Arnold
2009-10-26 19:39 ` Stuart D. Gathman
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=c268e4660910191141s5c5f3e1lf422c67f7f8bf423@mail.gmail.com \
--to=drew.kay@gmail.com \
--cc=larnolda1@gmail.com \
--cc=linux-lvm@redhat.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).