sys-fs/lvm2/files/lvm2-2.02.108-example.conf.in.patch

Maintainer note: Forward ported without editing from lvm2-2.02.99-example.conf.in.patch to apply cleanly.

--- conf/example.conf.in
+++ conf/example.conf.in
@@ -105,6 +105,10 @@
     # By default we accept every block device:
     # filter = [ "a/.*/" ]
 
+    # Gentoo: we exclude /dev/nbd by default, because it makes a lot of kernel
+    # noise when you probed while not available.
+    filter = [ "r|/dev/nbd.*|", "a/.*/" ]
+
     # Exclude the cdrom drive
     # filter = [ "r|/dev/cdrom|" ]
 
@@ -522,7 +526,8 @@
     # e.g. vgscan.lvm1 and they will stop working after you start using
     # the new lvm2 on-disk metadata format.
     # The default value is set when the tools are built.
-    # fallback_to_lvm1 = 0
+    # Gentoo: the LVM tools are a seperate package.
+    fallback_to_lvm1 = 0
 
     # The default metadata format that commands should use - "lvm1" or "lvm2".
     # The command line override is -M1 or -M2.
@@ -1182,12 +1187,13 @@
 
 # Metadata settings
 #
-# metadata {
+metadata {
     # Default number of copies of metadata to hold on each PV.  0, 1 or 2.
     # You might want to override it from the command line with 0 
     # when running pvcreate on new PVs which are to be added to large VGs.
 
-    # pvmetadatacopies = 1
+    # Gentoo: enable for data safety, but PV resize is then disabled.
+    # pvmetadatacopies = 2
 
     # Default number of copies of metadata to maintain for each VG.
     # If set to a non-zero value, LVM automatically chooses which of
@@ -1222,7 +1228,7 @@
     # the supplied toolset to make changes (e.g. vgcfgrestore).
 
     # dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
-#}
+}
 
 # Event daemon
 #