From: zkabelac@sourceware.org <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW man/lvm.8.in
Date: 1 Mar 2012 10:39:22 -0000 [thread overview]
Message-ID: <20120301103922.16292.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac at sourceware.org 2012-03-01 10:39:21
Modified files:
. : WHATS_NEW
man : lvm.8.in
Log message:
Add _rimage as reserved suffix
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2329&r2=1.2330
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/lvm.8.in.diff?cvsroot=lvm2&r1=1.8&r2=1.9
--- LVM2/WHATS_NEW 2012/03/01 10:30:48 1.2329
+++ LVM2/WHATS_NEW 2012/03/01 10:39:21 1.2330
@@ -1,5 +1,6 @@
Version 2.02.94 -
====================================
+ Add _rimage as reserved suffix to lvm.8 man page.
Improve error logging from mpath filter.
Check for allocation failure in hold_lock() in clvmd.
Use set_lv() (wipe initial 4KiB) for non zeroed thin volume.
--- LVM2/man/lvm.8.in 2011/11/03 14:38:37 1.8
+++ LVM2/man/lvm.8.in 2012/03/01 10:39:21 1.9
@@ -276,7 +276,7 @@
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', '_mimage', '_tdata', '_tmeta'.
+the strings '_mlog', '_mimage', '_rimage', '_tdata', '_tmeta'.
.SH DIAGNOSTICS
next reply other threads:[~2012-03-01 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 10:39 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-26 15:24 LVM2 ./WHATS_NEW man/lvm.8.in agk
2009-02-20 1:47 agk
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=20120301103922.16292.qmail@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@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.