http://bugzilla.novell.com/show_bug.cgi?id=495224 Summary: Imroper handling of multipath volumes? Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: --- Created an attachment (id=285908) --> (http://bugzilla.novell.com/attachment.cgi?id=285908) INformation about my disk system User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; hu-HU; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 I have a relatively copmlex disk layout, with many multipathed volumes for xen domains (see an attachment later). openSUSE 10.3's bootloader stuffs were able to handle this situation, while SLES 10 SP2 was unable, and now openSUSE 11.1 is also unable. For example, when I start YaST's bootloader configuration tool, it hangs in the "Chencking boot loader phase..." When I run mkinitrd, it creates the ram disks well, but the hangs FOREVER, because a child process of it (update-bootloader) hangs with ethernal 100% CPU usage. It means that I cannot even run a kernel update, because that process will hang forever. The only workaround is to restart the machine with unplugged fibrechannel optics (using the local /dev/sda disk only, which contains the dom0) in order to be able to update the kernel or the bootloader configuration. All of my fibrechannel multipath volumes (serving as disks for the domUs) are partitioned, many of them contain bootable (active) partitions, and some of them contain even installed grub bootloaders. In addition to the fact that yast2 modules hang, our storage system (Sun StorageTek 6140) is sending error reports during yast2 is struggling. These messages mean that the server's multipath subsystem is unnecessarily changing the paths to reach the fibrachannel volumes. Moreover, we are always getting these error messages during server startups! My idea is, that the root of this problem is that some disk-related subsystems (maybe the yas2 partitioner, boot loader conf., mkinitrd, and something during startup) tries to access the /dev files representing the separate paths, which is an incorrect behaviour. For example, I observed that accessing a partition on a separate path will lead to an error message (the device is busy or exclusively used, or something like that). Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.