From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Characters allowed for vg name
Date: Wed, 19 Mar 2008 14:21:44 +0000 [thread overview]
Message-ID: <20080319142144.GG12007@agk.fab.redhat.com> (raw)
In-Reply-To: <A78DB34D00374344A0AB65B6523C05DC02CDCF80@marsden.win.datacash.com>
On Wed, Mar 19, 2008 at 01:47:57PM -0000, Gerrard Geldenhuis wrote:
> I did report it as a bug via Redhat support. I have ended up pasting the
> mailinglist response in the support ticket after a week of no positive
> response.
Sorry for that: If you send me the ticket number privately I'll see that it's
progressed.
> Would you aggree that a short note about allowable names should be added
> to man lvm? If yes, then I don't mind creating a patch.
Here's a current summary of the rules (as added to bug 430907).
The characters allowed in VG and
LV names are: a-z A-Z 0-9 + _ . -
Neither a VG nor an LV can begin with a hyphen.
There are also various reserved names.
A VG cannot be called anything that appears in 'ls /dev' at the time it is
created (including '.' and '..' of course).
An LV can also not be called '.' or '..'.
A new LV cannot begin with the strings 'snapshot' or 'pvmove'.
It may not contain the strings '_mlog' or '_mimage'.
Additional reserved strings are likely to be added over time.
Pre-existing LVs may be found with these names, and the tools will normally cope
adequately. (Internally-generated LVs do use these reserved names - that's why
they are reserved.)
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2008-03-19 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 13:19 [linux-lvm] Characters allowed for vg name Gerrard Geldenhuis
2008-03-19 13:23 ` Bryn M. Reeves
2008-03-19 13:32 ` Milan Broz
2008-03-19 13:38 ` Alasdair G Kergon
2008-03-19 13:47 ` Gerrard Geldenhuis
2008-03-19 14:21 ` Alasdair G Kergon [this message]
2008-03-19 18:24 ` 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=20080319142144.GG12007@agk.fab.redhat.com \
--to=agk@redhat.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.