From: James Hawtin <oolon@ankh.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM Naming Convention
Date: Wed, 20 Apr 2011 10:01:49 +0100 [thread overview]
Message-ID: <4DAEA0FD.60709@ankh.org> (raw)
In-Reply-To: <2BF070A7A2375D46BA1B6087F8D5DCB67D93C8349E@seldmbx01.corpusers.net>
Assarsson, Emil wrote:
> We have also started to use hostnames in the VG names for the same reason. Starting with vg makes is easier to auto complete when using bash :-P. I don't see any reason why to use "lv" to the LV's but it doesn't hurt. I also try to use UUID's in the /etc/fstab as much as possible.
>
> Best regards
> Emil Assarsson
>
I also use the hostname in the volume group name for all the reasons
already suggest, its particularly valuable when dealing with san disk,
as any mistake is very obvious.
personally I use
/dev/<hostname>_<type><number>_vg/<filesystem>_lv
Where type is l for local disk s for san. I keep my raid 1 and raid 5 in
different volume groups to avoid mistakes, however both are called l or s.
Where the disk is for use to virtual machines I used
/dev/<hostname>_<type><number>_vg/<virtual machine>_v<number>_lv
I put _vg at the end of all volume groups mostly for completeness, and
avoidance of any change of a name clash, I also thing _lv is useful as
alots of devices can be mixed up in /dev/mapper so giving them a
seperate namespace so the don't get mixed up with multipathed disk, (and
in the old days raw devices) etc. I can do a ls /dev/mapper/*_lv to see
all my logical volumes all in one go, independant of group.
James
next prev parent reply other threads:[~2011-04-20 9:02 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
2011-04-20 6:48 ` Assarsson, Emil
2011-04-20 9:01 ` James Hawtin [this message]
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=4DAEA0FD.60709@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 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.