Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
LVM tools tried to connect to lvmetad even though the tools were run with the --sysinit option to denote the early system initialization where lvmetad may not have been running yet.
Consequence:
There were error messages "lvmetad.socket: connect failed: No such file or directory" issued multiple times during system initialization.
Fix:
There's an additional check whether LVM tool is running during early system initialization by checking the use of --sysinit option which is used in such cases.
Result:
If there's no lvmetad socket present while in early system initialization (while using --sysinit LVM command option), no error messages are issued about missing lvmetad socket if this is detected and LVM tools automatically fallback to non-lvmetad mode silently.
DescriptionCorey Marthaler
2013-10-07 17:50:14 UTC
Description of problem:
Isn't the one "WARNING: Failed to connect to lvmetad: ..." message enough to get the point across when lvmetad isn't running?
# If lvmetad has been running while use_lvmetad was 0, it MUST be stopped
# before changing use_lvmetad to 1 and started again afterwards.
use_lvmetad = 1
[root@harding-03 ~]# pvs
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
PV VG Fmt Attr PSize PFree
/dev/sda2 vg_harding03 lvm2 a-- 92.67g 0
[root@harding-03 ~]# lvs
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
/var/run/lvm/lvmetad.socket: connect failed: No such file or directory
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
lv_home vg_harding03 -wi-ao---- 33.36g
lv_root vg_harding03 -wi-ao---- 50.00g
lv_swap vg_harding03 -wi-ao---- 9.31g
Version-Release number of selected component (if applicable):
2.6.32-410.el6.x86_64
lvm2-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
lvm2-libs-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
lvm2-cluster-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
udev-147-2.48.el6 BUILT: Fri Aug 9 06:09:50 CDT 2013
device-mapper-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
device-mapper-libs-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
device-mapper-event-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
device-mapper-event-libs-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
cmirror-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013
This patch added more log messages for daemon handling code (daemon_open):
https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=981962b339123338335da5a3cda822117808c591
Those log messages are issued because at the time the "vgchange -aay --sysinit" is called in rc.sysinit, it's just too early to contact lvmetad - the lvm2-lvmetad initscript is started a bit later.
What we could do here is to automatically fallback to non-lvmetad mode if --sysinit option is used as that option is supposed for use during early bootup stage where some of the services are not supposed to be started yet (hmm, didn't we have this before, isn't this a regression with --sysinit + use_lvmetad=1?).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1387.html
Description of problem: Isn't the one "WARNING: Failed to connect to lvmetad: ..." message enough to get the point across when lvmetad isn't running? # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped # before changing use_lvmetad to 1 and started again afterwards. use_lvmetad = 1 [root@harding-03 ~]# pvs /var/run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory PV VG Fmt Attr PSize PFree /dev/sda2 vg_harding03 lvm2 a-- 92.67g 0 [root@harding-03 ~]# lvs /var/run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory /var/run/lvm/lvmetad.socket: connect failed: No such file or directory LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lv_home vg_harding03 -wi-ao---- 33.36g lv_root vg_harding03 -wi-ao---- 50.00g lv_swap vg_harding03 -wi-ao---- 9.31g Version-Release number of selected component (if applicable): 2.6.32-410.el6.x86_64 lvm2-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013 lvm2-libs-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013 lvm2-cluster-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013 udev-147-2.48.el6 BUILT: Fri Aug 9 06:09:50 CDT 2013 device-mapper-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013 device-mapper-libs-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013 device-mapper-event-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013 device-mapper-event-libs-1.02.79-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013 cmirror-2.02.100-4.el6 BUILT: Fri Sep 27 09:05:32 CDT 2013