On Fri, Oct 11, 2013 at 12:05:10PM -0400, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> When installing a boot loader into an LVM PV, blkid detects it as a
> dos partition table and does not probe the lvm superblock.
Yes, unfortunately this is currently unsupported scenario.
The libblkid checks for collision between LVM and filesystems/partition
tables to avoid very common situations when users use whole-disks
previously used by LVM in new setups with partition tables.
Unfortunately, partitioning tools usually does not wipe LVM header
from the device and it easy to create situation when there is
valid PT as well as valid LVM header.
So.. libblkid assumes that there is only LVM header within first 8K
of the device, because pvcreate wipes this area (try pvcreate again
and it will silently erase your grub!). If there is anything else
then the previously detected LVM is ignored.
Yes, it's really not perfect solution, but do we have any better
solution? Maybe it would be enough to improve the blkid partition
table parser to not interpret the boot loader with empty PT as a
valid PT. Not sure.
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
