[lvm-devel] Deadlock on "systemctl daemon-reload" when using socket based lvmetad activation.

[Peter Rajnoha]

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

-- 
Peter