<div dir="ltr">Hi Roger,<div><br></div><div>I have tried this with the older LVM package(.176) and this issue was not seen. Issue was seen with .180 version every time.</div><div># executing command: vgchange -ay <br>(status, output): (0, WARNING: Failed to connect to lvmetad. Falling back to device scanning.)<br> WARNING: Failed to connect to lvmetad. Falling back to device scanning.<br># executing command: pvcreate -ffy /dev/sda3<br>(status, output): (5, WARNING: Failed to connect to lvmetad. Falling back to device scanning.<br> Error reading device /dev/sda3 at 0 length 4096.<br> Error reading device /dev/ram0 at 0 length 4096.<br> Error reading device /dev/loop0 at 0 length 4096.<br> Error reading device /dev/sda at 0 length 512.<br> Error reading device /dev/sda at 0 length 4096.<br> Error reading device /dev/ram1 at 0 length 4096.<br> Error reading device /dev/sda1 at 0 length 4096.<br> Error reading device /dev/ram2 at 0 length 4096.<br> Error reading device /dev/sda2 at 0 length 4096.<br> Error reading device /dev/ram3 at 0 length 4096.<br> Error reading device /dev/ram4 at 0 length 4096.<br> Error reading device /dev/ram5 at 0 length 4096.<br> Error reading device /dev/ram6 at 0 length 4096.<br> Error reading device /dev/ram7 at 0 length 4096.<br> Error reading device /dev/ram8 at 0 length 4096.<br> Error reading device /dev/ram9 at 0 length 4096.<br> Error reading device /dev/ram10 at 0 length 4096.<br> Error reading device /dev/ram11 at 0 length 4096.<br> Error reading device /dev/ram12 at 0 length 4096.<br> Error reading device /dev/ram13 at 0 length 4096.<br> Error reading device /dev/ram14 at 0 length 4096.<br> Error reading device /dev/ram15 at 0 length 4096.<br> Device /dev/sda3 excluded by a filter.)<br>Failed to execute command: pvcreate -ffy /dev/sda3<br>ec=0<br></div><div><br></div><div>I have tried with different options of pvcreate but didnt helped much. After the system got halted with the above error, i tried to executing pvs command but got the below error.</div><div>bash-4.4# pvs<br> Error reading device /dev/ram0 at 0 length 4096.<br> Error reading device /dev/loop0 at 0 length 4096.<br> Error reading device /dev/sda at 0 length 512.<br> Error reading device /dev/sda at 0 length 4096.<br> Error reading device /dev/ram1 at 0 length 4096.<br> Error reading device /dev/sda1 at 0 length 4096.<br> Error reading device /dev/ram2 at 0 length 4096.<br> Error reading device /dev/sda2 at 0 length 4096.<br> Error reading device /dev/ram3 at 0 length 4096.<br> Error reading device /dev/sda3 at 0 length 4096.<br> Error reading device /dev/ram4 at 0 length 4096.<br> Error reading device /dev/sda4 at 0 length 4096.<br> Error reading device /dev/ram5 at 0 length 4096.<br> Error reading device /dev/ram6 at 0 length 4096.<br> Error reading device /dev/ram7 at 0 length 4096.<br> Error reading device /dev/ram8 at 0 length 4096.<br> Error reading device /dev/ram9 at 0 length 4096.<br> Error reading device /dev/ram10 at 0 length 4096.<br> Error reading device /dev/ram11 at 0 length 4096.<br> Error reading device /dev/ram12 at 0 length 4096.<br> Error reading device /dev/ram13 at 0 length 4096.<br> Error reading device /dev/ram14 at 0 length 4096.<br> Error reading device /dev/ram15 at 0 length 4096.<br> Error reading device /dev/sdb at 0 length 512.<br> Error reading device /dev/sdb at 0 length 4096.<br> Error reading device /dev/sdb1 at 0 length 4096.<br> Error reading device /dev/sdb2 at 0 length 4096.<br> Error reading device /dev/sdb3 at 0 length 4096.<br> Read-only locking type set. Write locks are prohibited.<br> Recovery of standalone physical volumes failed.<br> Cannot process standalone physical volumes<br>bash-4.4#<br></div><div><br></div><div>Attached the complete log in initial mail.</div><div><br></div><div>Thanks.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 14 Sep 2020 at 20:29, Roger Heflin <<a href="mailto:rogerheflin@gmail.com">rogerheflin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In general I would suggest fully disabling lvmetad from the config<br> files and from being started up.<br> <br> Issues around it not answering (like above) and answering but somehow<br> having stale/wrong info have burned me too many times to trust it. It<br> may be a lvmetad bug, or be udevd weirdness.<br> <br> The only significant improvement it makes is it reduces the lvm<br> command time on installs with significant numbers of devices, but<br> given that the info has been wrong often enough that is not worth the<br> risk.<br> <br> On Mon, Sep 14, 2020 at 2:25 AM KrishnaMurali Chennuboina<br> <<a href="mailto:krishchennu414@gmail.com" target="_blank">krishchennu414@gmail.com</a>> wrote:<br> ><br> > Hi Team,<br> ><br> > While trying to analyze one the issue, we felt that upgrading the current LVM2 package in our repository will be the best approach.<br> > 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.<br> ><br> > But while trying to boot mips64 hardware we have started observing the below issue. Providing the snippet of the log,<br> ><br> > # executing command: vgchange -an<br> > (status, output): (0, WARNING: Failed to connect to lvmetad. Falling back to device scanning.)<br> > WARNING: Failed to connect to lvmetad. Falling back to device scanning.<br> ><br> > Attached the detailed log for reference. There is no other change included other than the LVM2 update.<br> ><br> > LVM2 Version: 2.02.176<br> > Updated LVM2 version: 2.02.180<br> ><br> > Please share inputs on why this issue is being observed with .180 version?<br> > Please let me know if i can share any other information.<br> ><br> > Thanks.<br> ><br> > _______________________________________________<br> > linux-lvm mailing list<br> > <a href="mailto:linux-lvm@redhat.com" target="_blank">linux-lvm@redhat.com</a><br> > <a href="https://www.redhat.com/mailman/listinfo/linux-lvm" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/linux-lvm</a><br> > read the LVM HOW-TO at <a href="http://tldp.org/HOWTO/LVM-HOWTO/" rel="noreferrer" target="_blank">http://tldp.org/HOWTO/LVM-HOWTO/</a><br> <br> _______________________________________________<br> linux-lvm mailing list<br> <a href="mailto:linux-lvm@redhat.com" target="_blank">linux-lvm@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/linux-lvm" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/linux-lvm</a><br> read the LVM HOW-TO at <a href="http://tldp.org/HOWTO/LVM-HOWTO/" rel="noreferrer" target="_blank">http://tldp.org/HOWTO/LVM-HOWTO/</a><br> <br> </blockquote></div>