From: James Hawtin <oolon@ankh.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] N00b Question: Logical Volume without a Logical Volume Group ?
Date: Wed, 02 Nov 2011 10:18:50 +0000 [thread overview]
Message-ID: <4EB1190A.30501@ankh.org> (raw)
In-Reply-To: <604704853.1651560.1320172792894.JavaMail.root@sz0126a.westchester.pa.mail.comcast.net>
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 ?
>
>
It would have been possible to just build a filesystem directly on the
disk, to do a single partition with all the space, I would never do the
first thing as it is possible for other sysadmins easily make the
mistake of thinking the disk was blank, (particularly if it is not
mounted all the time). The second one is fine however the problem is if
you ever with to change to size of the partition, it is possible but it
is hard work.
Personally even with LVM I would still write a partition table the disk,
this helps show the disk as being used to other system administrators,
however there would be one partition on it of type 8e, and on that I
would create a PV (physical volume), this PV can then be used to create
a VG (Volume group) or be added to an exisiting one, when i create VGs I
normally use an ext size of arround 128m->256m to keep down the number
of disk fragments managed by the kernel. From that VG I can create an LV
(Logical Volume) Personally I would never allocate the whole space in a
volume group to an LV, even the volume group was just being used to join
disks together to make one huge filesystem, I try to keep by 5% of the
disk space this will allow the use of snapshots which are create for
keeping things consistent when backups are done.
As other posters have said, LVM always making changes to disk space much
easier, try the following with a partion table along...
Shrink 10g filesystem to 2g
Create another 2g filesystem
Expand first filesystem back to 8g
And another 10g peice of disk and add the space to the first filesystem.
James
next prev parent reply other threads:[~2011-11-02 10:18 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
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 [this message]
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=4EB1190A.30501@ankh.org \
--to=oolon@ankh.org \
--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