Hi, first it would be hard to guarantee nothing else tries to touch the remaining partitions. But the main issue is that multipath targets are created from the complete device and then, on top of the multipath volume, the tools create linear targets that represent the partitions. So you can't just use parts of a device through a multipath volume and other parts directly. Why not simply create a small SCSI disk that only has one partition with /boot on it? This one you can safely blacklist and use as a boot device. 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 13.07.2007 18:40:55: > Hi List, > I run SLES9 on IBM zSeries and I'm trying to hack a way to have my boot > partition on a multipath LUN and yet still be able to run IBM's zipl to > update the boot loader on that LUN. > The SLES9 has kernel 2.6.5-7.276-s390x, device-mapper-1.01.01-1.6, > multipath-tools-0.4.5-0.20. > > zipl won't update a multipath boot partition, zipl can't get the > geometry of a device-mapper device and quits with message > "Error: Could not get disk geometry"; this is a device-mapper > limitation, not zipl's fault. > > Since zipl needs a plain /dev/sdx boot device to update, > my hack idea is to put the boot partition on the multipath LUN and in > multipath.conf blacklist one of the LUN's paths (lets say /dev/sda) so > zipl can use /dev/sda to update the boot loader. I would unmount the > multipath boot partition device from /boot, mount /dev/sda at /boot and > then run zipl. > > Any ideas how risky this would be: I/O to the LUN's non-boot partitions > via multipaths and zipl I/O to the LUN's boot partition via the > blacklisted path? > -------------------------------------------------------- > This e-mail, including any attachments, may be confidential, > privileged or otherwise legally protected. It is intended only for > the addressee. If you received this e-mail in error or from someone > who was not authorized to send it to you, do not disseminate, copy > or otherwise use this e-mail or its attachments. Please notify the > sender immediately by reply e-mail and delete the e-mail from your system. > > > -- > 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
