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: 89bc1aa324

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 '89bc1aa324'

${ noResults }

dracut/modules.d/90lvm

History

Benjamin Marzinski 9dd9329f7a modules.d: fix udev rules detection of multipath devices ... Starting with the 0.7.7 release of the multipath tools, the multipath udev rules always set a value in ENV{DM_MULTIPATH_DEVICE_PATH} for any device that multipath scans. A value of 0 means that the device is not claimed by multipath, and a value of 1 means that it is. Because of this, udev rules that check ENV{DM_MULTIPATH_DEVICE_PATH}=="?*" will always return True, and act as if every scanned device is claimed by multipath. Checking ENV{DM_MULTIPATH_DEVICE_PATH}=="1" will work correctly for both the old and new versions of the multipath tools.		6 years ago
..
64-lvm.rules	modules.d: fix udev rules detection of multipath devices	6 years ago
lvm_scan.sh	…
module-setup.sh	…
parse-lvm.sh	…