Comment 12 for bug 719129

> Why does it try to call kpartx when dmraid has already created
> the devices?

If I recall correctly, kpartx did not create the device entries if dmraid had not been used to activate the device.

> For that matter, why does it need to run dmraid at all?
> Libparted already takes care of creating the new
> devices for you.

Older versions of libparted, or versions of libparted configured with --disable-device-mapper do not create the /dev/mapper entries.

The GParted code was developed to work with dev-mapper dmraid devices before libparted was able to deal with these accordingly.