allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
Xenial amd64 VM running lvm2 commands returns this output:
various vgcreate/lvcreate returns this message:
allocation/
Falling back to native LVM signature detection.
Logical volume "lv2" created.
For example:
$ sudo pvcreate /dev/vdg
allocation/
Falling back to native LVM signature detection.
Physical volume "/dev/vdg" successfully created
Google shows this upstream commit:
https:/
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
ProcVersionSign
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_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in lvm2 (Ubuntu): | |
importance: | Undecided → High |
Status changed to 'Confirmed' because the bug affects multiple users.