Bug 1443392 - lvm2 update takes a long time
Summary: lvm2 update takes a long time
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marian Csontos
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-19 07:38 UTC by Marko Myllynen
Modified: 2019-03-25 14:54 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-25 14:54:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1367686 0 high CLOSED error log lvmetad[745]: Failed to accept connection 2021-09-08 20:44:52 UTC

Internal Links: 1367686

Description Marko Myllynen 2017-04-19 07:38:36 UTC
Description of problem:
At least since the latest lvm2 update (lvm2-2.02.166-1.el7_3.4.x86_64) Yum spends a long time (~90 seconds) in the clean up phase of lvm2; pstree(1) shows a postscript is executing "systemctl try-restart lvm2-lvmetad.service". This has been observed on some machines, and even on them sporadically, doing "systemctl try-restart lvm2-lvmetad.service" afterwards may get stuck once but then work ok later on.

Apr 19 10:00:01 localhost systemd: Stopping LVM2 metadata daemon...
Apr 19 10:00:01 localhost lvmetad[569]: Failed to accept connection errno 11.
Apr 19 10:01:31 localhost systemd: lvm2-lvmetad.service stop-sigterm timed out. Killing.
Apr 19 10:01:31 localhost systemd: lvm2-lvmetad.service: main process exited, code=killed, status=9/KILL
Apr 19 10:01:31 localhost systemd: Unit lvm2-lvmetad.service entered failed state.
Apr 19 10:01:31 localhost systemd: lvm2-lvmetad.service failed.
Apr 19 10:01:31 localhost systemd: Started LVM2 metadata daemon.
Apr 19 10:01:31 localhost systemd: Starting LVM2 metadata daemon...
Apr 19 10:01:31 localhost systemd: Reloading.

Please try to make the "systemctl try-restart lvm2-lvmetad.service" operation faster in all cases.

Version-Release number of selected component (if applicable):
lvm2-2.02.166-1.el7_3.4.x86_64

Comment 2 Marian Csontos 2017-04-19 19:03:16 UTC
It is reproducible. This seems the problem:

> Apr 19 10:00:01 localhost lvmetad[569]: Failed to accept connection errno 11.

Comment 3 David Teigland 2017-04-19 19:16:19 UTC
Similar issue was dealt with here

https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=b12961e7ebd6fb29d760daafd3c16e4ba3e54e80

An lvmetad core or lvmetad gdb backtrace would probably help.

Comment 4 Marko Myllynen 2017-04-20 08:12:57 UTC
I tried to reproduce this by downgrading lvm2/device-mapper packages on few machines where I saw this and then upgrading again but the issue did not occur.

Currently I am unable to provide more information.

Thanks.

Comment 5 Jonathan Earl Brassow 2017-04-26 16:03:55 UTC
(In reply to Marian Csontos from comment #2)
> It is reproducible. This seems the problem:
> 
> > Apr 19 10:00:01 localhost lvmetad[569]: Failed to accept connection errno 11.

Marian, if you can reproduce, can you provide the info dave is looking for?

Comment 6 Marian Csontos 2017-04-27 15:47:22 UTC
"Reproducible" is not the right word. "Common" would be better. Second attempt to try-restart was executed immediately. If seen again I will try to get more details.

Comment 7 Marian Csontos 2019-03-25 14:54:25 UTC
No data collected in two years. Closing this...


Note You need to log in before you can comment on or make changes to this bug.