Arch Linux

IAmRoot

Member

From: Germany

Registered: 2018-08-08

Posts: 3

[SOLVED] Long shutdown times

Hi,

I am experiencing long shutdown times on my computer.

Versions:
Kernel: 5.0.3-arch1-1-ARCH
lvm2: 2.02.183-2
systemd: systemd 241 (241.7-2-arch)

shutdown-log:

[   29.865882] watchdog: watchdog0: watchdog did not stop!
[   29.866606] printk: systemd-shutdow: 48 output lines suppressed due to ratelimiting
[   29.879997] systemd-shutdown[1]: Syncing filesystems and block devices.
[   29.885345] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[   29.890970] systemd-journald[299]: Received SIGTERM from PID 1 (systemd-shutdow).
[  119.890137] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[  119.892913] systemd-shutdown[1]: Sending SIGKILL to PID 306 (lvmetad).
[  119.893271] systemd-shutdown[1]: Hardware watchdog 'iTCO_wdt', version 0
[  119.893648] systemd-shutdown[1]: Unmounting file systems.
[  119.894081] [1894]: Remounting '/' read-only in with options '(null)'.
[  119.911355] EXT4-fs (nvme0n1p8): re-mounted. Opts: (null)
[  119.922477] systemd-shutdown[1]: All filesystems unmounted.
[  119.922478] systemd-shutdown[1]: Deactivating swaps.
[  119.922508] systemd-shutdown[1]: All swaps deactivated.
[  119.922509] systemd-shutdown[1]: Detaching loop devices.
[  119.922941] systemd-shutdown[1]: All loop devices detached.
[  119.922943] systemd-shutdown[1]: Detaching DM devices.
[  119.934199] EXT4-fs (nvme0n1p8): re-mounted. Opts: data=ordered

I think there is something with lvmetad, but I haven't found the issue yet.
I already tried this "https://bbs.archlinux.org/viewtopic.php?id=225129", but it didn't help.

systemctl status lvm2-monitor.service

● lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling
   Loaded: loaded (/usr/lib/systemd/system/lvm2-monitor.service; enabled; vendor preset: disabled)
   Active: active (exited) since Sun 2019-03-24 18:34:28 CET; 5min ago
     Docs: man:dmeventd(8)
           man:lvcreate(8)
           man:lvchange(8)
           man:vgchange(8)
  Process: 302 ExecStart=/usr/bin/lvm vgchange --monitor y --ignoreskippedcluster (code=exited, status=0/SUCCESS)
 Main PID: 302 (code=exited, status=0/SUCCESS)

Mar 24 18:34:28 jans-nb-02 systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Can anyone help?

Last edited by IAmRoot (2019-03-30 15:52:35)

loqs

Member

Registered: 2014-03-06

Posts: 17,440

Re: [SOLVED] Long shutdown times

Please try the mitigation's from https://bbs.archlinux.org/viewtopic.php?id=245020

IAmRoot

Member

From: Germany

Registered: 2018-08-08

Posts: 3

Re: [SOLVED] Long shutdown times

Please try the mitigation's from https://bbs.archlinux.org/viewtopic.php?id=245020

Thanks for the link.

I set "use_lvmetad = 0" in /etc/lvm/lvm.conf.

Now the shutdown times are back to normal again.