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

Dne 3.9.2016 v 05:17 james harvey napsal(a): On Tue, Aug 16, 2016 at 5:57 AM, Zdenek Kabelac wrote: Dne 6.8.2016 v 04:08 james harvey napsal(a): Same problem and question about if an immediate SIGKILL is OK for dmeventd. On Thu, Aug 4, 2016 at 11:20 PM, james harvey

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

Same problem and question about if an immediate SIGKILL is OK for dmeventd. On Thu, Aug 4, 2016 at 11:20 PM, james harvey wrote: > Does it matter at all if lvmetad shuts down gracefully? > > Can I safely just have systemd right off the bat send a SIGKILL? > > Most

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

Does it matter at all if lvmetad shuts down gracefully? Can I safely just have systemd right off the bat send a SIGKILL? Most things I wouldn't ask about, but I'm wondering if this is PURELY a caching daemon where gracefully shutting down doesn't really do anything. On Wed, Aug 3, 2016 at 10:51

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

On Wed, Aug 3, 2016 at 10:51 PM, james harvey wrote: > After upgrading to systemd v231, my shutdowns/reboots have a 90 second > delay at the very end. Linux kvm 4.6.4-1. Ignore the "kvm" here, must have typed that into the wrong window. This is on a physical system,

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

After upgrading to systemd v231, my shutdowns/reboots have a 90 second delay at the very end. Linux kvm 4.6.4-1. After I looked into it, I found it's due to lvmetad never terminating when receiving a SIGTERM, and after 90 seconds, systemd performs a SIGKILL. systemd 231 (commit d4506129)