Public bug reported: Xenial amd64 VM running lvm2 commands returns this output:
various vgcreate/lvcreate returns this message: allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Logical volume "lv2" created. For example: $ sudo pvcreate /dev/vdg allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Physical volume "/dev/vdg" successfully created Google shows this upstream commit: https://www.redhat.com/archives/lvm-devel/2015-September/msg00148.html Either we shouldn't set this value by default, or lvm2 should be compiled with the support. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu1 ProcVersionSignature: User Name 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 Date: Mon Jan 11 19:34:07 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1532915 Title: allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Status in lvm2 package in Ubuntu: New Bug description: Xenial amd64 VM running lvm2 commands returns this output: various vgcreate/lvcreate returns this message: allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Logical volume "lv2" created. For example: $ sudo pvcreate /dev/vdg allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Physical volume "/dev/vdg" successfully created Google shows this upstream commit: https://www.redhat.com/archives/lvm-devel/2015-September/msg00148.html Either we shouldn't set this value by default, or lvm2 should be compiled with the support. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu1 ProcVersionSignature: User Name 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 Date: Mon Jan 11 19:34:07 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1532915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
