public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: wysochanski@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/man lvm.8 Date: Thu, 20 Mar 2008 18:34:00 -0000 [thread overview] Message-ID: <20080320183429.11931.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: wysochanski@sourceware.org 2008-03-20 18:34:29 Modified files: man : lvm.8 Log message: Add LV and VG name restrictions to the lvm man page. Original patch by: Gerrard Geldenhuis <Gerrard.Geldenhuis@datacash.com> Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/lvm.8.diff?cvsroot=lvm2&r1=1.12&r2=1.13 --- LVM2/man/lvm.8 2008/01/11 20:24:25 1.12 +++ LVM2/man/lvm.8 2008/03/20 18:34:29 1.13 @@ -257,6 +257,16 @@ The volume group name that is assumed for any reference to a logical volume that doesn't specify a path. Not set by default. +.SH VALID NAMES +The following characters are valid for VG and LV names: +\fBa-z A-Z 0-9 + _ . -\fP +.LP +VG and LV names cannot begin with a hyphen. +There are also various reserved names that are used internally by lvm that can not be used as LV or VG names. +A VG cannot be called anything that exists in /dev/ at the time of creation, nor can it be called '.' or '..'. +A LV cannot be called '.' '..' 'snapshot' or 'pvmove'. The LV name may also not contain the strings '_mlog' or '_mimage' + + .SH DIAGNOSTICS All tools return a status code of zero on success or non-zero on failure. .SH FILES
next reply other threads:[~2008-03-20 18:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-20 18:34 wysochanski [this message] -- strict thread matches above, loose matches on Subject: below -- 2008-01-11 20:24 wysochanski 2008-01-11 19:24 wysochanski
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=20080320183429.11931.qmail@sourceware.org \ --to=wysochanski@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).