Using device-mapper volumes for partioning is wrong in the way DM works. DM devices do not use partitions and do not support the ioctl used to update the partition table (exception for linear mappings with single devices). Partitions on multipath volumes are created by kpartx as linear targets after creating the base multipath target. The only safe way that should always be used is to remove the multipath volume (multipath -f <mpname>), then call fdisk on the sd device (optionally call blockdev --rereadpt <dev> on all other paths) and the recreate the multipath volume by calling multipath. Mit freundlichem Gruß / Regards, Stefan Bader SW Linux on zSeries Development Stefan.Bader@xxxxxxxxxx IBM Deutschland Entwicklung GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Herbert Kircher Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 ---------------------------------------------------------------------------------- When all other means of communication fail, try words. dm-devel-bounces@xxxxxxxxxx wrote on 28.09.2007 22:28:06: > When I perform an fdisk or sfdisk on a /dev/mapper/ multipath device I > get a warning about it failing to re-read the partition information. > With fdisk it warns that I'll need to reboot before using the device, > with sfdisk it just complains about the ioctl that failed: > > Re-reading the partition table ... > BLKRRPART: Invalid argument > > Is it possible I have something configured wrong? Or is this a problem > with the way /dev/mapper nodes work? I get the same result when using > /dev/dm-* nodes. With the raw device nodes such as /dev/sd* it works > ok. > > -- > dm-devel mailing list > dm-devel@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/dm-devel -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
