Hi Roger,
I have tried this with the older LVM package(.176) and this issue was not
seen. Issue was seen with .180 version every time.
# executing command: vgchange -ay
(status, output): (0, WARNING: Failed to connect to lvmetad. Falling back
to device scanning.)
WARNING: Failed to connect to
Hi all,
I am testing lvmcache with VDO and I have issue with devices block size.
The big & slow VDO device is on top of a 4-disk MD RAID 10 device
(itself on top of dm-integrity). Over the VDO device I created a
thinpool and a thinvol [1]. When adding the cache device to the volume
group via v
In general I would suggest fully disabling lvmetad from the config
files and from being started up.
Issues around it not answering (like above) and answering but somehow
having stale/wrong info have burned me too many times to trust it. It
may be a lvmetad bug, or be udevd weirdness.
The only si
Hi Team,
While trying to analyze one the issue, we felt that upgrading the current
LVM2 package in our repository will be the best approach.
As part of that, we have updated the respective package from 2.02.176 to
2.02.180. We have verified the same and booted x86_64 hardware without any
issues.
