From: Digimer <linux@alteeve.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Dan White <ygor@comcast.net>
Subject: Re: [linux-lvm] N00b Question: Logical Volume without a Logical Volume Group ?
Date: Tue, 01 Nov 2011 15:20:50 -0400 [thread overview]
Message-ID: <4EB04692.3060705@alteeve.com> (raw)
In-Reply-To: <1190544765.1654069.1320174833294.JavaMail.root@sz0126a.westchester.pa.mail.comcast.net>
On 11/01/2011 03:13 PM, Dan White wrote:
> ----- Digimer <linux@alteeve.com> wrote:
>> On 11/01/2011 02:39 PM, Dan White wrote:
>>> Is a logical volume group necessary before one can start making mountable partitions ?
>>>
>>> I'm trying to work with a SAN. We were allocated a 10Gb LUN to "play" with. Another admin created a logical volume on the LUN and then made a single partition out of the logical volume. The flow I am familiar with from Red Hat's GUI is to first make a logical volume group, then make partitions in the group that I can adjust in size as necessary.
>>>
>>> Are both workflows valid ?
>>
>> LVs must be created from VGs.
>>
>
> I agree. Got a documentation reference I can use for backup ?
man lvcreate? Not being flippant, but the 'VolumeGroupName' is a
required value. :)
Also from the man page;
DESCRIPTION
lvcreate creates a new logical volume in a volume group ( see
vgcre-
ate(8), vgchange(8) ) by allocating logical extents from the free
phys-
ical extent pool of that volume group. If there are not enough
free
physical extents then the volume group can be extended ( see
vgex-
tend(8) ) with other physical volumes or by reducing existing
logical
volumes of this volume group in size ( see lvreduce(8) ). If you
spec-
ify one or more PhysicalVolumes, allocation of physical extents
will be
restricted to these volumes.
The second form supports the creation of snapshot logical volumes
which
keep the contents of the original logical volume for backup purposes.
--
Digimer
E-Mail: digimer@alteeve.com
Freenode handle: digimer
Papers and Projects: http://alteeve.com
Node Assassin: http://nodeassassin.org
"omg my singularity battery is dead again.
stupid hawking radiation." - epitron
next prev parent reply other threads:[~2011-11-01 19:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 18:39 [linux-lvm] N00b Question: Logical Volume without a Logical Volume Group ? Dan White
2011-11-01 18:45 ` Digimer
2011-11-01 19:13 ` Dan White
2011-11-01 19:20 ` Digimer [this message]
2011-11-01 19:51 ` Dan White
2011-11-02 14:02 ` Mark H. Wood
2011-11-01 21:09 ` Ray Morris
2011-11-02 10:18 ` James Hawtin
2011-11-02 11:41 ` Marek Podmaka
2011-11-02 13:37 ` James Hawtin
2011-11-02 14:18 ` Mark H. Wood
2011-11-02 14:50 ` Marek Podmaka
2011-11-02 14:56 ` James Hawtin
2011-11-02 15:06 ` Dan White
2011-11-02 16:39 ` James Hawtin
2011-11-02 17:30 ` Eugene Vilensky
2011-11-02 18:23 ` Dan White
2011-11-02 18:41 ` Dan White
2011-11-02 17:57 ` Galen Seitz
2011-11-03 6:53 ` Marek Podmaka
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=4EB04692.3060705@alteeve.com \
--to=linux@alteeve.com \
--cc=linux-lvm@redhat.com \
--cc=ygor@comcast.net \
/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