dracut/modules.d/90dm
Lukas Wunner 5729ae8029 90dm/dm-shutdown.sh: dmsetup remove_all -> dmsetup remove
The function 99shutdown/shutdown.sh:_check_shutdown() assumes that
shutdown scripts report success or failure via their return value.
However, "dmsetup remove_all" always reports success, even if some
of the device mappings could not be removed.

I submitted a patch for dmsetup but the lvm2 folks rejected it,
asserting that its behaviour is correct, that "remove_all" should
only be used by developers and that the proper solution would be
to invoke "dmsetup remove" on each device. This does report success
or failure via the return value.

Apart from fixing that issue, this commit also adds the dmsetup
option "--noudevsync". Without it, dmsetup would hang after removal
of a device while trying to communicate with systemd-udevd, which
is no longer running at this shutdown stage.

[harald: replaces backticks with $() ]
2015-02-19 10:57:08 +01:00
..
11-dm.rules dm: add 11-dm.rules for udev-168 and cleanup-db 2011-05-02 10:55:44 +02:00
59-persistent-storage-dm.rules split 95udev-rules/59-persistent-storage.rules to md and dm modules 2013-03-07 15:01:47 +01:00
dm-pre-udev.sh remove all vim and emacs code format comments 2014-08-29 13:38:47 +02:00
dm-shutdown.sh 90dm/dm-shutdown.sh: dmsetup remove_all -> dmsetup remove 2015-02-19 10:57:08 +01:00
module-setup.sh remove all vim and emacs code format comments 2014-08-29 13:38:47 +02:00