[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] lvmetad doesn't terminate with SIGTERM if thin volume used

On Mon, Sep 5, 2016 at 4:39 AM, Zdenek Kabelac <zkabelac redhat com> wrote:
> Dne 3.9.2016 v 05:17 james harvey napsal(a):
>> 1) Should the lvm2-lvmetad, dm-event, and lvm2-monitor unit files be
>> modified so they are never given a SIGKILL?  Even with
>> lvm2-monitor.service enabled, even on Fedora, if systemd sees they
>> don't SIGTERM/SIGINT within 90 seconds (systemd v231 is 90 seconds,
>> was 10 second before), it's sending them a SIGKILL.  I think adding
>> "SendSIGKILL=no" to the Service and Socket sections will do this, if I
>> understand it correctly.
> That's a different story here - it something is 'deadlocked' and
> can't move forward - killing things after 90 seconds can't make
> the situation any more worst likely - especially if you are doing
> shutdown...
> So no - there is no plan to use such option (SendSIGKILL=no) ATM
> (State-machine is pretty complex and when some devices are 'forgotten' in
> suspend - it's quite hard to fix it).

Can monitoring actions be expected to take more than 90 seconds?  I'm
assuming some of them are, but I could be totally wrong here.

If they aren't expected to take that long, my question has no point,
as yes, if something's deadlocked killing them won't make anything

If they aren't expected to take that long, a refusal to allow a
SIGKILL to prevent a possible leaving the system in a dizzy state
seems to me to outweigh the chance of it being deadlocked.  (Just my
thoughts of course.)

>> 2) Should lvm2-lvmetad and dm-event systemd unit files want
>> lvm2-monitor.service?
> lvm2-lvmetad is unrelated to monitoring service (dmevent).

Sorry, I'm confused here.  Not sure what you mean here.  I'm meaning
should lvm2-lvmetad want lvm2-monitor, and should dm-event want
lvm2-monitor.  Nothing between lvm2-lvmetad and dm-event.

If lvm2-monitor is disabled, lvm2-lvmetad ignores a SIGINT, unless the
user manually stops monitoring.  If lvm2-monitor is disabled, dm-event
ignores a SIGINT, unless the user stops monitoring.

If running lvm2-lvmetad or dm-event without lvm2-monitor is a crazy
idea, seems like pushing a user toward having it would be a good idea.
Again just my thoughts.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]