LVM2/doc example.conf.in

LVM2/doc example.conf.in

[zkabelac]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	zkabelac@sourceware.org	2012-05-23 12:59:35

Modified files:
	doc            : example.conf.in 

Log message:
	Move thin_check_executable to proper section
	
	It's read from global section.
	In-release change, so no what's new

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.50&r2=1.51

--- LVM2/doc/example.conf.in	2012/05/14 16:29:50	1.50
+++ LVM2/doc/example.conf.in	2012/05/23 12:59:35	1.51
@@ -467,6 +467,21 @@
     # proper udev rules, all changes in block device configuration will be
     # *ignored* until a manual 'vgscan' is performed.
     use_lvmetad = 0
+
+    # Full path of the utility called to check that a thin metadata device
+    # is in a state that allows it to be used.
+    # Each time a thin pool needs to be activated or after it is deactivated
+    # this utility is executed. The activation will only proceed if the utility
+    # has an exit status of 0.
+    # Set to "" to skip this check.  (Not recommended.)
+    # The thin tools are available as part of the device-mapper-persistent-data
+    # package from https://github.com/jthornber/thin-provisioning-tools.
+    #
+    thin_check_executable = "@THIN_CHECK_CMD@"
+
+    # String with options passed with thin_check command. By default,
+    # option '-q' is for quiet output.
+    thin_check_options = [ "-q" ]
 }
 
 activation {
@@ -654,20 +669,6 @@
     thin_pool_autoextend_threshold = 100
     thin_pool_autoextend_percent = 20
 
-    # Full path of the utility called to check that a thin metadata device
-    # is in a state that allows it to be used.
-    # Each time a thin pool needs to be activated, this utility is executed.
-    # The activation will only proceed if the utility has an exit status of 0.
-    # Set to "" to skip this check.  (Not recommended.)
-    # The thin tools are available as part of the device-mapper-persistent-data
-    # package from https://github.com/jthornber/thin-provisioning-tools.
-    #
-    thin_check_executable = "@THIN_CHECK_CMD@"
-
-    # String with options passed with thin_check command. By default,
-    # option '-q' is for quiet output.
-    thin_check_options = [ "-q" ]
-
     # While activating devices, I/O to devices being (re)configured is
     # suspended, and as a precaution against deadlocks, LVM2 needs to pin
     # any memory it is using so it is not paged out.  Groups of pages that

LVM2/doc example.conf.in

[agk]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	agk@sourceware.org	2012-05-14 16:29:51

Modified files:
	doc            : example.conf.in 

Log message:
	Refer to details of snapshot of raid problem.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.49&r2=1.50

--- LVM2/doc/example.conf.in	2012/05/10 00:18:49	1.49
+++ LVM2/doc/example.conf.in	2012/05/14 16:29:50	1.50
@@ -430,8 +430,12 @@
     # "mirror" - The original RAID1 implementation provided by LVM2/DM.  It is
     # 	         characterized by a flexible log solution (core, disk, mirrored)
     #		 and by the necessity to block I/O while reconfiguring in the
-    #		 event of a failure.  Snapshots of this type of RAID1 can be
-    #		 problematic.
+    #		 event of a failure.
+    #
+    #		 There is an inherent race in the dmeventd failure handling
+    #		 logic with snapshots of devices using this type of RAID1 that
+    #		 in the worst case could cause a deadlock.
+    #		   Ref: https://bugzilla.redhat.com/show_bug.cgi?id=817130#c10
     #
     # "raid1"  - This implementation leverages MD's RAID1 personality through
     # 	       	 device-mapper.  It is characterized by a lack of log options.

LVM2/doc example.conf.in

[agk]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	agk@sourceware.org	2012-05-10 00:18:49

Modified files:
	doc            : example.conf.in 

Log message:
	Uncomment allocation section to match style of rest of file.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.48&r2=1.49

--- LVM2/doc/example.conf.in	2012/04/27 18:37:42	1.48
+++ LVM2/doc/example.conf.in	2012/05/10 00:18:49	1.49
@@ -190,40 +190,38 @@
 
 # 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 = [ "@*" ]
-#
-#    Changes made in version 2.02.85 extended the reach of the 'cling'
-#    policies to detect more situations where data can be grouped
-#    onto the same disks.  Set this to 0 to revert to the previous
-#    algorithm.
-#
-#    maximise_cling = 1
-#
-#    Set to 1 to guarantee that mirror logs will always be placed on 
-#    different PVs from the mirror images.  This was the default
-#    until version 2.02.85.
-#
-#    mirror_logs_require_separate_pvs = 0
-#
-#    Set to 1 to guarantee that thin pool metadata will always
-#    be placed on different PVs from the pool data.
-#
-#    thin_pool_metadata_require_separate_pvs = 0
-#}
+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 = [ "@*" ]
+
+    # Changes made in version 2.02.85 extended the reach of the 'cling'
+    # policies to detect more situations where data can be grouped
+    # onto the same disks.  Set this to 0 to revert to the previous
+    # algorithm.
+    maximise_cling = 1
+
+    # Set to 1 to guarantee that mirror logs will always be placed on 
+    # different PVs from the mirror images.  This was the default
+    # until version 2.02.85.
+    mirror_logs_require_separate_pvs = 0
+
+    # Set to 1 to guarantee that thin pool metadata will always
+    # be placed on different PVs from the pool data.
+    thin_pool_metadata_require_separate_pvs = 0
+}
 
 # This section that allows you to configure the nature of the
 # information that LVM2 reports.

LVM2/doc example.conf.in

[jbrassow]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	jbrassow@sourceware.org	2012-04-27 18:37:42

Modified files:
	doc            : example.conf.in 

Log message:
	Make a note that "raid1" is not cluster-aware in the example lvm.conf.
	
	In the description of the segment types for the 'mirror_segtype_default'
	field, we mention that "raid1" is not cluster-aware.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.47&r2=1.48

--- LVM2/doc/example.conf.in	2012/03/14 17:13:45	1.47
+++ LVM2/doc/example.conf.in	2012/04/27 18:37:42	1.48
@@ -441,6 +441,8 @@
     #		 on the same device as the image - no separate devices are
     #		 required.)  This mirror implementation does not require I/O
     #		 to be blocked in the kernel in the event of a failure.
+    #		 This mirror implementation is not cluster-aware and cannot be
+    #		 used in a shared (active/active) fashion in a cluster.
     #
     # Specify the '--type <mirror|raid1>' option to override this default
     # setting.

LVM2/doc example.conf.in

[zkabelac]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	zkabelac@sourceware.org	2012-03-14 17:13:45

Modified files:
	doc            : example.conf.in 

Log message:
	Cleanup for conf file

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.46&r2=1.47

--- LVM2/doc/example.conf.in	2012/03/14 17:12:05	1.46
+++ LVM2/doc/example.conf.in	2012/03/14 17:13:45	1.47
@@ -661,8 +661,8 @@
     thin_check_executable = "@THIN_CHECK_CMD@"
 
     # String with options passed with thin_check command. By default,
-    # option '-q' is for quite output.
-    thin_check_options = [ "-q", 121e321 ]
+    # option '-q' is for quiet output.
+    thin_check_options = [ "-q" ]
 
     # While activating devices, I/O to devices being (re)configured is
     # suspended, and as a precaution against deadlocks, LVM2 needs to pin

LVM2/doc example.conf.in

[prajnoha]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	prajnoha@sourceware.org	2011-04-26 09:09:24

Modified files:
	doc            : example.conf.in 

Log message:
	Uncomment obtain_device_list_from_udev setting in lvm.conf.
	
	Just for consistency with other settings we already have in lvm.conf.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.23&r2=1.24

--- LVM2/doc/example.conf.in	2011/04/22 12:05:32	1.23
+++ LVM2/doc/example.conf.in	2011/04/26 09:09:24	1.24
@@ -27,7 +27,7 @@
     # fully. LVM2 needs to be compiled with udev support for this setting to
     # take effect. N.B. Any device node or symlink not managed by udev in
     # udev directory will be ignored with this setting on.
-    # obtain_device_list_from_udev = 1
+    obtain_device_list_from_udev = 1
 
     # If several entries in the scanned directories correspond to the
     # same block device and the tools need to display a name for device,

LVM2/doc example.conf.in

[snitzer]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	snitzer@sourceware.org	2011-04-12 20:44:42

Modified files:
	doc            : example.conf.in 

Log message:
	fix s/then/than/ typos in 'pv_min_size' section and fold floppy example
	into documentation preamble.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.19&r2=1.20

--- LVM2/doc/example.conf.in	2011/02/27 00:38:32	1.19
+++ LVM2/doc/example.conf.in	2011/04/12 20:44:41	1.20
@@ -147,11 +147,10 @@
 
     # Minimal size (in KB) of the block device which can be used as a PV.
     # In clustered environment all nodes have to use the same value.
-    # Any value smaller then 512KB is ignored.
-    pv_min_size = 512
-
-    # Example: Ignore devices smaller then 2MB (i.e. floppy drives).
+    # Any value smaller than 512KB is ignored.
+    # Example: Ignore devices smaller than 2MB (i.e. floppy drives).
     # pv_min_size = 2048
+    pv_min_size = 512
 }
 
 # This section allows you to configure the way in which LVM selects

LVM2/doc example.conf.in

[mornfall]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	mornfall@sourceware.org	2010-10-13 15:45:19

Modified files:
	doc            : example.conf.in 

Log message:
	Tweak the lvm.conf comment about devices/disable_after_error_count.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.12&r2=1.13

--- LVM2/doc/example.conf.in	2010/10/13 15:40:38	1.12
+++ LVM2/doc/example.conf.in	2010/10/13 15:45:18	1.13
@@ -136,9 +136,10 @@
     # in recovery situations.
     ignore_suspended_devices = 0
 
-    # During each LVM operation any errors received from a device are counted.
-    # If this counter exceeds the number here, no further I/O is sent to the
-    # device.
+    # During each LVM operation errors received from each device are counted.
+    # If the counter of a particular device exceeds the limit set here, no
+    # further I/O is sent to that device for the remainder of the respective
+    # operation.
     disable_after_error_count = 0
 
     # Allow use of pvcreate --uuid without requiring --restorefile.

LVM2/doc example.conf.in

[snitzer]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	snitzer@sourceware.org	2010-08-25 13:06:03

Modified files:
	doc            : example.conf.in 

Log message:
	Make example.conf description for 'default_data_alignment' more generic.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.10&r2=1.11

--- LVM2/doc/example.conf.in	2010/08/20 22:24:58	1.10
+++ LVM2/doc/example.conf.in	2010/08/25 13:06:03	1.11
@@ -99,8 +99,7 @@
     md_chunk_alignment = 1
 
     # Default alignment of the start of a data area in MB.  If set to 0,
-    # a small value of 64KB will be used, which was the default until
-    # LVM2 version 2.02.73.  Set to 1 for 1MiB, 2 for 2MiB, etc.
+    # a value of 64KB will be used.  Set to 1 for 1MiB, 2 for 2MiB, etc.
     # default_data_alignment = @DEFAULT_DATA_ALIGNMENT@
 
     # By default, the start of a PV's data area will be a multiple of

LVM2/doc example.conf.in

[wysochanski]

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski@sourceware.org	2010-06-28 20:40:16

Modified files:
	doc            : example.conf.in 

Log message:
	Update example.conf.in to describe vgmetadatacopies.
	
	Update example.conf to describe vgmetadatacopies.  Provide an
	explanation for the '0' ("unmanaged") value.
	
	Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/example.conf.in.diff?cvsroot=lvm2&r1=1.2&r2=1.3

--- LVM2/doc/example.conf.in	2010/05/20 13:47:21	1.2
+++ LVM2/doc/example.conf.in	2010/06/28 20:40:15	1.3
@@ -456,6 +456,17 @@
 
     # pvmetadatacopies = 1
 
+    # Default number of copies of metadata to hold on each VG.
+    # If set to a non-zero value, LVM automatically manages the PV
+    # 'metadataignore' flags (see pvchange) to achieve the requested
+    # copies of metadata.  You may set a value larger than the
+    # the sum of all metadata areas on all physical volumes.  This value
+    # can be overridden on the command line of various commands. The
+    # default value of 0 indicates that LVM should not automatically
+    # manage the 'metadataignore' flags.
+
+    # vgmetadatacopies = 0
+
     # Approximate default size of on-disk metadata areas in sectors.
     # You should increase this if you have large volume groups or
     # you want to retain a large on-disk history of your metadata changes.