Bug 1335561 - lvm versions higher than 2.02.150 cause systemd issues
Summary: lvm versions higher than 2.02.150 cause systemd issues
Keywords:
Status: CLOSED DUPLICATE of bug 1334063
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.153
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-12 13:51 UTC by Hussam Al-Tayeb
Modified: 2016-05-16 08:49 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-16 08:49:52 UTC
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?


Attachments (Terms of Use)

Description Hussam Al-Tayeb 2016-05-12 13:51:47 UTC
if I do systemctl daemon-reexec, there are zombie systemd-gpt something and other systemd-something processes. They stay there for a whole minute and block bus connections in the meantime.

This started happening after 2.02.151 lvm update.
The last version that did not cause this was 2.02.150

This is mostly an annoyance since the zombie processes do disappear after a minute and "systemctl something" operations start working again.
However in that whole minute, I get errors connecting to bus if I "systemctl start something".

Comment 1 Hussam Al-Tayeb 2016-05-12 14:34:23 UTC
The only non-zombie systemd generator process was the lvm one. so it appears to have been stuck for a minute or so.

Comment 2 Peter Rajnoha 2016-05-16 08:07:03 UTC
This is also reported as bug #1334063 (for Fedora rawhide).

Comment 3 Hussam Al-Tayeb 2016-05-16 08:49:52 UTC
Ok, thank you. I will mark it as duplicate since that one was reported earlier :)

*** This bug has been marked as a duplicate of bug 1334063 ***


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