Extend cling allocation policy to recognise PV tags (cling_by_tags).

Add allocation/cling_tag_list to lvm.conf.

1 files changed, 19 insertions, 0 deletions

diff --git a/doc/example.conf.in b/doc/example.conf.in
index ac9aae70..8504f5dc 100644
--- a/doc/example.conf.in
+++ b/doc/example.conf.in
@@ -146,6 +146,25 @@ devices {
     require_restorefile_with_uuid = 1
 }
 
+# This section allows you to configure the way in which LVM selects
+# free space for its Logical Volumes.
+#allocation {
+#    When searching for free space to extend an LV, the "cling"
+#    allocation policy will choose space on the same PVs as the last
+#    segment of the existing LV.  If there is insufficient space and a
+#    list of tags is defined here, it will check whether any of them are
+#    attached to the PVs concerned and then seek to match those PV tags
+#    between existing extents and new extents.
+#    Use the special tag "@*" as a wildcard to match any PV tag.
+#    
+#    Example: LVs are mirrored between two sites within a single VG.
+#    PVs are tagged with either @site1 or @site2 to indicate where
+#    they are situated.
+#
+#    cling_tag_list = [ "@site1", "@site2" ]
+#    cling_tag_list = [ "@*" ]
+#}
+
 # This section that allows you to configure the nature of the
 # information that LVM2 reports.
 log {