Arch Linux

loewexy

Member

Registered: 2017-04-12

Posts: 2

lvmetad and dmeventd delay shutdown

Hey everyone,

lately I have a problem on my Laptop running Arch. The Shutdown is delayed by 90 seconds. I have made a shutdown log which shows the following:

[   92.155662] systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
[   92.155688] systemd[1]: Set hardware watchdog to 10min.
[   92.155697] watchdog: watchdog0: watchdog did not stop!
[   92.273931] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[   92.280654] systemd-udevd[366]: Unload module index
[   92.280842] systemd-udevd[366]: Unloaded link configuration context.
[   92.284941] systemd-journald[328]: Received SIGTERM from PID 1 (systemd-shutdow).
[   92.284974] systemd-journald[328]: systemd-journald stopped as pid 328
[  182.281647] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[  182.283943] systemd-shutdown[1]: Sending SIGKILL to PID 483 (lvmetad).
[  182.284015] systemd-shutdown[1]: Sending SIGKILL to PID 506 (dmeventd).
[  182.284219] systemd-shutdown[1]: Process 1354 (plymouthd) has been marked to be excluded from killing. It is running from the root file system, and thus likely to block re-mounting of the root file system to read-only. Please consider moving it into an initrd file system instead.
[  182.286242] systemd-shutdown[1]: Hardware watchdog 'iTCO_wdt', version 0
[  182.286590] systemd-shutdown[1]: Unmounting file systems.

which tells me that lvmetad and dmeventd did not respond to the SIGTERM signal, and therefore get killed after the timeout of 90 seconds. If I try to stop them manually with

sudo systemctl stop lvm2-lvmetad.service

I get this status

~$ sudo systemctl status lvm2-lvmetad.service
● lvm2-lvmetad.service - LVM2 metadata daemon
   Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; disabled; vendor preset: disabled)
   Active: deactivating (stop-sigterm) since Wed 2017-04-12 21:56:16 CEST; 4s ago
     Docs: man:lvmetad(8)
 Main PID: 496 (lvmetad)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/lvm2-lvmetad.service
           └─496 /usr/bin/lvmetad -f

Apr 12 21:56:16 lukas-netbook systemd[1]: Stopping LVM2 metadata daemon...
Apr 12 21:56:16 lukas-netbook lvmetad[496]: Failed to accept connection errno 11.

and after 90 seconds I get

~$ sudo systemctl status lvm2-lvmetad.service
● lvm2-lvmetad.service - LVM2 metadata daemon
   Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmetad.service; disabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Wed 2017-04-12 21:57:46 CEST; 2s ago
     Docs: man:lvmetad(8)
  Process: 496 ExecStart=/usr/bin/lvmetad -f (code=killed, signal=KILL)
 Main PID: 496 (code=killed, signal=KILL)

Apr 12 21:56:16 lukas-netbook systemd[1]: Stopping LVM2 metadata daemon...
Apr 12 21:56:16 lukas-netbook lvmetad[496]: Failed to accept connection errno 11.
Apr 12 21:57:46 lukas-netbook systemd[1]: lvm2-lvmetad.service: State 'stop-sigterm' timed out. Killing.
Apr 12 21:57:46 lukas-netbook systemd[1]: lvm2-lvmetad.service: Killing process 496 (lvmetad) with signal SIGKILL.
Apr 12 21:57:46 lukas-netbook systemd[1]: lvm2-lvmetad.service: Main process exited, code=killed, status=9/KILL
Apr 12 21:57:46 lukas-netbook systemd[1]: Stopped LVM2 metadata daemon.
Apr 12 21:57:46 lukas-netbook systemd[1]: lvm2-lvmetad.service: Unit entered failed state.
Apr 12 21:57:46 lukas-netbook systemd[1]: lvm2-lvmetad.service: Failed with result 'timeout'.

For dmeventd the results are the same. Here also the daemon gets killed because it does not respond to SIGTERM.

Now I don't know how to go on in debugging. Why don't they react to to SIGTERM? How can I debug this Issue further?

Regards
Lukas

njam

Member

Registered: 2017-05-04

Posts: 6

Re: lvmetad and dmeventd delay shutdown

If it's the same problem I experienced, then it can be solved by:

sudo systemctl enable lvm2-monitor.service
sudo systemctl start lvm2-monitor.service

See:
https://bugs.archlinux.org/index.php?do … k_id=50420
https://www.mail-archive.com/dm-devel@r … 02361.html

loewexy

Member

Registered: 2017-04-12

Posts: 2

Re: lvmetad and dmeventd delay shutdown

That might be the problem yes. But for another problem probably caused by arch I changed the notebook temporarily to Ubuntu, so I can not test this at the moment. But thanks for you answer I try if I have the problem again.