You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: ae43adb70d

master

0.1

0.2

0.3

0.4

0.5

0.6

0.7

0.8

0.9

001

002

003

004

005

006

007

008

009

010

011

012

013

014

015

016

017

018

019

020

021

022

023

024

025

026

027

028

029

030

031

032

033

033-502

034

035

036

037

038

039

040

041

042

043

044

045

046

047

048

049

050

051

052

053

054

055

056

RHEL-7.1

RHEL-7.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'ae43adb70d'

${ noResults }

dracut/modules.d/90dm

History

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 $() ]		10 years ago
..
11-dm.rules	…
59-persistent-storage-dm.rules	…
dm-pre-udev.sh	remove all vim and emacs code format comments	11 years ago
dm-shutdown.sh	90dm/dm-shutdown.sh: dmsetup remove_all -> dmsetup remove	10 years ago
module-setup.sh	remove all vim and emacs code format comments	11 years ago