I believe Philip may be incorrect about the dmraid rule not belonging.
I have a RAID 5 disk with a GPT partition table. When only dmraid
runs, my drive is listed in /dev/mapper/drive but not its partitions.
If I then run 'kpartx -a /dev/mapper/drive' then my two partitions
appear as /dev/mapper/drive1 and /dev/mapper/drive2 which can both be
mounted. Therefore kpartx must run even after dmraid already added the
tables since dmraid cannot handle GPT partition tables. Note that you
are right that this is not needed for standard MBR tables.
When I changed the case in the dmraid rule from 'dmraid-*' to 'DMRAID-*'
I can now mount my partitions via /etc/fstab using UUID as per usual.
However, this causes a duplication of mappings for my disks with MBR.
Is there a way to make this rule only fire for disks with GPT?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/737027
Title:
kpartx udev rule is broken
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
