15.10: Long boot-time delays trying to find disconnected hot-plugged storage devices

Bug #1491393 reported by TJ
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Is there a way to prevent systemd from creating generator targets for hot-plug disks?

Currently it is causing very long delays at boot-time - which are not interruptible by the sys-admin - but I'm not sure at what point systemd decided those hot-plug devices should be added to the boot-time tasks, or how to safely delete them.

There are generator rules added at some stage but I cannot find information on how to safely remove them, or how to prevent them being created.

In this output the device-mapper names prefixed LUKS_HDD_ are the problem:

$ ls -l /var/run/systemd/generator/*
-rw-r--r-- 1 root root 486 Sep 2 11:45 /var/run/systemd/generator/boot.mount
-rw-r--r-- 1 root root 486 Sep 2 11:45 /var/run/systemd/generator/home.mount
-rw-r--r-- 1 root root 294 Sep 2 11:45 /var/run/systemd/generator/-.mount
-rw-r--r-- 1 root root 933 Sep 2 11:45 /var/run/systemd/generator/systemd-cryptsetup@LUKS_BOOT.service
-rw-r--r-- 1 root root 933 Sep 2 11:45 /var/run/systemd/generator/systemd-cryptsetup@LUKS_DATA.service
-rw-r--r-- 1 root root 887 Sep 2 11:45 /var/run/systemd/generator/systemd-cryptsetup@LUKS_HDD_OS.service
-rw-r--r-- 1 root root 887 Sep 2 11:45 /var/run/systemd/generator/systemd-cryptsetup@LUKS_HDD_VM.service
-rw-r--r-- 1 root root 929 Sep 2 11:45 /var/run/systemd/generator/systemd-cryptsetup@LUKS_OS.service
-rw-r--r-- 1 root root 491 Sep 2 11:45 /var/run/systemd/generator/usr-local.mount
-rw-r--r-- 1 root root 485 Sep 2 11:45 /var/run/systemd/generator/var.mount

Revision history for this message
Martin Pitt (pitti) wrote :

You should be able to add the "noauto" option to the devices in /etc/crypttab which you don't rely on for booting.

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.