From: Andrey Borzenkov <arvidjaar@gmail.com>
To: lvm-devel@redhat.com
Subject: Deadlock on "systemctl daemon-reload" when using socket based lvmetad activation.
Date: Thu, 20 Feb 2014 20:30:57 +0400 [thread overview]
Message-ID: <20140220203057.131ff519@opensuse.site> (raw)
In-Reply-To: <5305C97A.7000002@redhat.com>
? Thu, 20 Feb 2014 10:23:06 +0100
Peter Rajnoha <prajnoha@redhat.com> ?????:
> On 02/20/2014 09:36 AM, Peter Rajnoha wrote:
> > On 02/19/2014 09:14 PM, Andrey Borzenkov wrote:
> >> Details are in https://bugzilla.novell.com/show_bug.cgi?id=862076#c44
> >> and following comment.
> >>
> >> Always starting lvmetad really defeats the idea of socket activation
> >> (do not start process until needed) and does not fully eliminate the
> >> problem (consider lvmetad crashing in the wrong moment).
> >>
> >
> > I agree. I'm not even counting much that anybody uses lvmetad by
> > enabling the lvm2-lvmetad.service itself (though possible) - this was
> > primarily designed to be socket-based activated. The socket-based
> > activation should just work under all circumstances. I'll fix that...
>
> Actually, this should be already fixed in lvm2 v2.02.99 with this commit:
>
> https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=983f0b46f2de85b8de0e2d7f8afbdf53f132a87a
>
Yes, this fixes it. Thank you!
prev parent reply other threads:[~2014-02-20 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 20:14 Deadlock on "systemctl daemon-reload" when using socket based lvmetad activation Andrey Borzenkov
2014-02-20 8:36 ` Peter Rajnoha
2014-02-20 9:23 ` Peter Rajnoha
2014-02-20 16:30 ` Andrey Borzenkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140220203057.131ff519@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=lvm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.