registry team mailing list archive

[Curtis Gedak <gedakc@xxxxxxxxx>]

Phillip,

If the upstream dmraid command has changed the way it names partitions,
then perhaps kpartx is no longer required.

In the past, GParted required kpartx because dmraid did not follow the
partition naming guidelines outlined in the general rule of thumb listed
in comment #11.

In fact this difference in behaviour is a good part of the reason why I
wrote the DMRaid.cc source code file in the first place.  At that time
dmraid was not directly supported by libparted-1.8.8.  It was necessary
to ensure that the dmraid partition names matched the names that
libparted would generate.  Also device entries for the new partitions
were not automatically created when the partition table was changed
using libparted.

The kpartx command is used to create these device entries so that they
match with the partition names generated by libparted.  GParted then
uses these partition names as arguments to external commands such as
mkfs.ext2.


Danny,

Thanks for posting your work.  I took a look at the patch code, and this
lead me to believe that perhaps you still had kpartx installed on your
system when you tested with your two dmraid setups.

Would you be able to check if kpartx is still installed on your test
system?

If so, could you try removing kpartx and then re-running your tests?

-- 
Gparted does not list dmraid devices
https://bugs.launchpad.net/bugs/554582
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for GParted.