summaryrefslogtreecommitdiff
path: root/conf
diff options
context:
space:
mode:
authorAlasdair G Kergon <agk@redhat.com>2014-04-18 02:46:34 +0100
committerAlasdair G Kergon <agk@redhat.com>2014-04-18 02:46:34 +0100
commitb5f8f452ac563ef07513e770b3202c6dc209443c (patch)
treec75307dffc7318a7855730afa0589fe851cb688f /conf
parent17e304e0ac24ba0d1887badfb51afa731aa138e9 (diff)
downloadlvm2-b5f8f452ac563ef07513e770b3202c6dc209443c.tar.gz
tools: Add --readonly support.
Offer lock-free access to display virtual machine or clustered VG metadata while it might be in use.
Diffstat (limited to 'conf')
-rw-r--r--conf/example.conf.in9
1 files changed, 9 insertions, 0 deletions
diff --git a/conf/example.conf.in b/conf/example.conf.in
index 2ed3fd65a..d5ddb1c5b 100644
--- a/conf/example.conf.in
+++ b/conf/example.conf.in
@@ -520,6 +520,15 @@ global {
# Type 3 uses built-in clustered locking.
# Type 4 uses read-only locking which forbids any operations that might
# change metadata.
+ # Type 5 offers dummy locking for tools that do not need any locks.
+ # You should not need to set this directly: the tools will select when
+ # to use it instead of the configured locking_type. Do not use lvmetad or
+ # the kernel device-mapper driver with this locking type.
+ # It is used by the --readonly option that offers read-only access to
+ # Volume Group metadata that cannot be locked safely because it belongs to
+ # an inaccessible domain and might be in use, for example a virtual machine
+ # image or a disk that is shared by a clustered machine.
+ #
# N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
# supported in clustered environment. If use_lvmetad=1 and locking_type=3
# is set at the same time, LVM always issues a warning message about this