[parted-devel] [RFC] do not create device-mapper nodes and rely on udev/kpartx instead

[Petr Uzel]

Hello,

Phillip's recent device-mapper patch series reminded me one SUSE patch
(attached) which I wanted to post as a RFC for quite some time.

To make the story short: In SUSE, we have been bitten several times by
discrepancies between how parted and udev/kpartx create device nodes for
device mapper devices. Instead of keeping these in sync (which is one
of the goals of Phillip's patches IIUC), we decided to patch
parted so that it does not add/remove device-mapper devices on its own
and instead relies on udev/kpartx to do it (parted just issues 'change'
uevent on the device which has been changed).

The patch is in production since at least SLE11-SP1 (or maybe even
longer) and I'm not aware of any issues with it.

Reportedly, this patch fixes RH bug
https://bugzilla.redhat.com/show_bug.cgi?id=698121
to which I don't have access, though. CCing IBM guys who
should have more information about the background of this bug and who
tested the patch in their environment.

Please note that the attached patch is just a RFC, applies to
parted-2.4, contains ugly hack with system("udevadm settle") and also
misses removal of few functions which are no longer needed with this
patch.

The question is: Would this concept be acceptable for parted upstream?

Petr

--
Petr Uzel
IRC: ptr_uzl @ freenode
-------------- next part --------------
A non-text attachment was scrubbed...
Name: do-not-create-dm-nodes.patch
Type: text/x-patch
Size: 1786 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/parted-devel/attachments/20120111/f6f945cc/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/parted-devel/attachments/20120111/f6f945cc/attachment.pgp>