From: Joe Pruett <joey@q7.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM Naming Convention
Date: Tue, 19 Apr 2011 15:36:41 -0700 [thread overview]
Message-ID: <4DAE0E79.3090503@q7.com> (raw)
In-Reply-To: <4DAE0B5E.4090503@stanford.edu>
i have started putting the hostname in my vg names as well, mainly so
that if i have to move the drives to another system for upgrades,
crashes, etc, i don't get collisions between the local vg and the one
i'm hooking up temporarily.
On 04/19/2011 03:23 PM, Mike Seda wrote:
> Hi All,
> Recently, I came across the new LVM naming convention in RHEL 6. This
> convention places the output of "hostname -s" in the VG name. This
> doesn't really fit into the way I've previously setup VGs, which was
> to create a new VG for each type of disk attached to the system, e.g.
> RAID 1 SAS 10K (local), RAID 6 SATA 7.2K (SAN).
>
> I guess I could modify the naming convention slightly as shown below:
> - /dev/vg_`hostname -s`_[0-9][0-9]/lv_{foo|bar}
>
> Another thought I had was that maybe I don't need a separate VG for
> each type of disk since the lvcreate/lvextend commands seem to be able
> to create/grow an LV by PV. My understanding is that this would allow
> you to skip the step of growing the VG by the PV, right?
>
> Essentially, I'm just wondering what other folks in my situation are
> doing for LVM naming.
>
> Thanks In Advance,
> Mike
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2011-04-19 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 22:23 [linux-lvm] LVM Naming Convention Mike Seda
2011-04-19 22:36 ` Joe Pruett [this message]
2011-04-20 6:48 ` Assarsson, Emil
2011-04-20 9:01 ` James Hawtin
2011-04-20 15:33 ` Males, Jess
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=4DAE0E79.3090503@q7.com \
--to=joey@q7.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.