-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/11/2012 12:21 PM, Petr Uzel wrote: > 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).
What if kpartx does not create the device? Up until I just patched it the other day ( still pending upload ), Ubuntu doesn't run kpartx on to recognize partitions on dmraid disks. Upstream parted needs to work correctly whether or not the system automatically runs kpartx. By the way, when I patched ubuntu to run kpartx, I ran into a bug in kpartx and posted a patch to [email protected]. Udev runs it on /dev/dm-0 instead of /dev/mapper/foo, and it was using the former name to decide if it should add the 'p' partition separator before the partition number. This resulted in it creating partitions named /dev/mapper/foop1 instead of /dev/mapper/foo1. Does SUSE not have this problem? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPDdbVAAoJEJrBOlT6nu75dBQH/jszzWBNPSwzfxkuK9V+zTRK YQi8HbsS3/00HnSNYJvnSOE8fTBLeL8+uHtqyBgTnGIA6fAnmCcMfagSt21cvCOi bl8HOWYuSSSqw1HXxxSHw7VTBva+v1OXynB27W7NjpuA5aJlbbVUSTq7cO04UUYm nICxnb5U+hHqSYIEMq4Cq15S8t1w0GwcpCvE/SgUCkyA3iKJmqEPgqP870J/OQl7 m0fOIh3Yy57YmRKsQm0Mtaijr5TYuOu4BzwINX149YSrD5/14TyEqWGA7GO02+NS 7puiVD2cOqGL8G0GZP2BzhJE1sDq7bR84rhUV1h+0sLkqjKifl98dWRBqpQqhVU= =lz6D -----END PGP SIGNATURE-----
