-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue(Failed to connect to lvmetad. Falling back to device scanning) after upgrading LVM2 to 2.02.180 #38
Comments
executing command: pvcreate -ffy /dev/sda3(status, output): (1280, File descriptor 3 leaked on pvcreate invocation. Parent PID 1138: sh |
Closing as lvmetad has been dropped from 'main' branch and as such is no longer needed/developed/supported. |
lvm_bootupIssue.txt
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.
But while trying to boot mips64 hardware we have started observing the below issue. Providing the snippet of the log,
executing command: vgchange -an
(status, output): (0, WARNING: Failed to connect to lvmetad. Falling back to device scanning.)
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Attached the detailed log for reference. There is no other change included other than the LVM2 update.
LVM2 Version: 2.02.176Updated LVM2 version: 2.02.180
Please share inputs on why this issue is being observed with .180 version? Please let me know if i can share any other information.
The text was updated successfully, but these errors were encountered: