Skip to contentSkip to conversation

PATCH: Fix / on lvm

PATCH Hans de Goede 3 participants 4 messages Jul 10, 2009 – Jul 13, 2009 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

Currently / on lvm is not working because the udev rules test for KERNEL="dm-*" which of course will not be true for PV's, so PV's are not recognized and thus lvm does not work.

The attached patch fixes this.

Regards,

Hans

modules.d/90lvm/64-lvm-vol_id.rules +0 -1
index d4b5269..0ebf009 100644
@@ -6,7 +6,6 @@
 
 SUBSYSTEM!="block", GOTO="lvm_end"
 ACTION!="add|change", GOTO="lvm_end"
-KERNEL!="dm-*", GOTO="lvm_end"
 
 IMPORT{program}="vol_id --export $tempnode"
 
modules.d/90lvm/64-lvm.rules +0 -1
index 3eddd07..7218862 100644
@@ -6,7 +6,6 @@
 
 SUBSYSTEM!="block", GOTO="lvm_end"
 ACTION!="add|change", GOTO="lvm_end"
-KERNEL!="dm-*", GOTO="lvm_end"
 
 IMPORT{program}="/sbin/blkid -o udev -p $tempnode"
 
#2 lore raw
In reply to a message not in the archive
Quoted 7 lines · Hans de Goede

Hi,

Currently / on lvm is not working because the udev rules test for KERNEL="dm-*" which of course
will not be true for PV's, so PV's are not recognized and thus lvm does not work.

Quoted 5 lines

The attached patch fixes this.

Regards,

Hans

Could you please describe in detail the type of setup needed to reproduce this failure? I have / on lvm here and dracut is working just fine.

Warren Togami
[email protected]
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#4 lore raw
In reply to a message not in the archive

Hi,

Quoted 10 lines · Warren Togami
Quoted 9 lines · Hans de Goede

Hi,

Currently / on lvm is not working because the udev rules test for KERNEL="dm-*" which of course
will not be true for PV's, so PV's are not recognized and thus lvm does not work.

The attached patch fixes this.

Quoted 8 lines
Quoted 3 lines

Regards,

Hans

Could you please describe in detail the type of setup needed to reproduce this failure? I have / on lvm here and dracut is working just fine.

Basically the default anaconda partitioning setup so /boot /dev/sda1 (sata disk) and / on an lv whose vg contains one (large) pv which is /dev/sda2

But this isn't all that interesting, read the rules, they are there to
do: "lvm vgscan; lvm vgchange -ay" when a new PV gets added to the system, yet they contain the line:

KERNEL!="dm-*", GOTO="lvm_end"

Before doing this, meaning that a PV on a regular scsi disk (instead of a PV on top of device mapper) will not cause the
"lvm vgscan; lvm vgchange -ay" to get executed and thus my / to not be found.

Maybe you are using a dmraid setup ? That would explain why these rules are working for you.

Regards,

Hans

--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#5 lore raw
In reply to a message not in the archive
Quoted 7 lines · Hans de Goede

Hi,

Currently / on lvm is not working because the udev rules test for KERNEL="dm-*" which of course
will not be true for PV's, so PV's are not recognized and thus lvm does not work.

Quoted 5 lines

The attached patch fixes this.

Regards,

Hans

fixed
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html