pre-release

diff --git a/VERSION b/VERSION
index 680848d38c487a57af90dd0dea59f3e353b2694c..7909645160fe41aee0edf79061187e07f43a31db 100644 (file)
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-2.02.153(2)-git (2016-04-30)
+2.02.153(2)-git (2016-05-07)

diff --git a/VERSION_DM b/VERSION_DM
index 1eb63a8c401ed55248a60748fc537544a994f3f8..17bcab08d1084545bc23d9fb3d06460c2b04a9f4 100644 (file)
--- a/VERSION_DM
+++ b/VERSION_DM
@@ -1 +1 @@
-1.02.125-git (2016-04-30)
+1.02.124-git (2016-05-07)

diff --git a/WHATS_NEW b/WHATS_NEW
index c8cee7648ed1e43184a34a177963bc6ebff9714b..721d8b7c0c1cf94fc16a16e1dfda4008fc0b725f 100644 (file)
--- a/WHATS_NEW
+++ b/WHATS_NEW
@@ -1,5 +1,5 @@
-Version 2.02.153 - 
-==================================
+Version 2.02.153 - 7th May 2016
+===============================
   Change warning messages related to duplicate PVs.
   A named device is always processed itself, not switched for a duplicate.
   Add PV attr "d" and report field "duplicate" for duplicate PVs.

diff --git a/WHATS_NEW_DM b/WHATS_NEW_DM
index f6392efda0a74a0051bfddd34ec1a4aad0f14839..24561d404f5d2c1970078a7467c93b13b97368a9 100644 (file)
--- a/WHATS_NEW_DM
+++ b/WHATS_NEW_DM
@@ -1,6 +1,3 @@
-Version 1.02.125 - 
-==================================
-
 Version 1.02.124 - 30th April 2016
 ==================================
   Add dm_udev_wait_immediate to libdevmapper for waiting outside the library.

diff --git a/conf/example.conf.in b/conf/example.conf.in
index a6a6762b499fed9bd01ac94fc6d4d10ff856b30c..c34481e9bae1c4e312d28e86ef4066757f633d67 100644 (file)
--- a/conf/example.conf.in
+++ b/conf/example.conf.in
@@ -299,6 +299,19 @@ devices {
        # generally do. If enabled, discards will only be issued if both the
        # storage and kernel provide support.
        issue_discards = 0
+
+       # Configuration option devices/allow_changes_with_duplicate_pvs.
+       # Allow VG modification while a PV appears on multiple devices.
+       # When a PV appears on multiple devices, LVM attempts to choose the
+       # best device to use for the PV. If the devices represent the same
+       # underlying storage, the choice has minimal consequence. If the
+       # devices represent different underlying storage, the wrong choice
+       # can result in data loss if the VG is modified. Disabling this
+       # setting is the safest option because it prevents modifying a VG
+       # or activating LVs in it while a PV appears on multiple devices.
+       # Enabling this setting allows the VG to be used as usual even with
+       # uncertain devices.
+       allow_changes_with_duplicate_pvs = 0
 }
 
 # Configuration section allocation.