From: agk@sourceware.org <agk@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/man lvm.conf.5.in
Date: 12 Jan 2012 02:32:10 -0000 [thread overview]
Message-ID: <20120112023210.13835.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk at sourceware.org 2012-01-12 02:32:09
Modified files:
man : lvm.conf.5.in
Log message:
Add activation/read_only_volume_list to override LV permission in metadata.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/lvm.conf.5.in.diff?cvsroot=lvm2&r1=1.22&r2=1.23
--- LVM2/man/lvm.conf.5.in 2011/10/04 20:45:36 1.22
+++ LVM2/man/lvm.conf.5.in 2012/01/12 02:32:09 1.23
@@ -423,6 +423,18 @@
\fBtags\fP above).
Logical volume and volume groups can also be included in the list
by name e.g. vg00, vg00/lvol1.
+.IP
+\fBread_only_volume_list\fP \(em This acts as a filter through
+which all requests to activate a logical volume on this machine
+are passed. A logical volume is activated in read-only mode (instead
+of read-write) if it matches an item in the list. Volumes must first
+pass the \fBvolume_list\fP filter, if present. Tags must be preceded
+by @ and are checked against all tags defined in the logical volume
+and volume group metadata for a match.
+@* is short-hand to check every tag set on the host machine (see
+\fBtags\fP above).
+Logical volume and volume groups can also be included in the list
+by name e.g. vg00, vg00/lvol1.
.TP
\fBmetadata\fP \(em Advanced metadata settings
.IP
next reply other threads:[~2012-01-12 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 2:32 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-04 20:45 LVM2/man lvm.conf.5.in agk
2011-04-12 21:21 snitzer
2011-03-10 15:20 zkabelac
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=20120112023210.13835.qmail@sourceware.org \
--to=agk@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.