This can make probelems with zvol that have lvm pools on it. --- patchdir/filter_zvols_in_lvm.conf.patch | 15 +++++++++++++++ patchdir/series | 1 + 2 files changed, 16 insertions(+) create mode 100644 patchdir/filter_zvols_in_lvm.conf.patch
diff --git a/patchdir/filter_zvols_in_lvm.conf.patch b/patchdir/filter_zvols_in_lvm.conf.patch new file mode 100644 index 0000000..13cc07b --- /dev/null +++ b/patchdir/filter_zvols_in_lvm.conf.patch @@ -0,0 +1,15 @@ +Index: LVM2.2.02.116/conf/example.conf.in +=================================================================== +--- LVM2.2.02.116.orig/conf/example.conf.in ++++ LVM2.2.02.116/conf/example.conf.in +@@ -39,6 +39,10 @@ devices { + # to use with LVM2. + scan = [ "/dev" ] + ++ # Do not scann ZFS zvols ++ # This can make problems on ZFS dataset ++ filter = [ "r|/dev/zd*|" ] ++ + # Select external device information source to use for further and more + # detailed device determination. Some information may already be available + # in the system and LVM2 can use this information to determine the exact diff --git a/patchdir/series b/patchdir/series index a532d19..24ec03c 100644 --- a/patchdir/series +++ b/patchdir/series @@ -15,3 +15,4 @@ jessie-remove-udebs.patch configure-with-corosync2.patch fix-changelog.patch fix-symbols.patch +filter_zvols_in_lvm.conf.patch -- 2.1.4 _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel