[Bug 493327] New: openSUSE's bootloader configuring tools cannot handle my complex multipathed disc structure
http://bugzilla.novell.com/show_bug.cgi?id=493327 Summary: openSUSE's bootloader configuring tools cannot handle my complex multipathed disc structure Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 I have a relatively comlex 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 in order to be able to update the kernel or the bootloader configuration. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c1
--- Comment #1 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c2
--- Comment #2 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c3
--- Comment #3 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493327
User aschnell@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c5
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c6
--- Comment #6 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c7
Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493327
User aschnell@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c8
--- Comment #8 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c9
--- Comment #9 from Tamás Németh
Please open a second bug-report for the issues you mention in comment #7.
And what about he partitioner? Does it also need a separate bugreport? -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=493327
User aschnell@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c10
Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c11
--- Comment #11 from Tamás Németh
AFAIS you are not patient enough. With about 100 disks storage probing can be slow and you killed YaST while it was still probing disk partitions. That should be the case for bootloader and partitioner.
OK, but once I observed a kernel update (including some mkinitrd stuff) was running for more than 24 hours! -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c12
--- Comment #12 from Tamás Németh
http://bugzilla.novell.com/show_bug.cgi?id=493327
User aschnell@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c13
--- Comment #13 from Arvin Schnell
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c14
--- Comment #14 from Tamás Németh
Maybe the slowness is caused by the issues mentioned in comment #7. But debugging that is beyond the task of bugzilla.
I have and idea: Those are multipath volumes, but beside the /dev files representing the combined multipath devices, some disk subsystems (maybe 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). -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=493327
User nice@titanic.nyme.hu added comment
http://bugzilla.novell.com/show_bug.cgi?id=493327#c15
--- Comment #15 from Tamás Németh
Please open a second bug-report for the issues you mention in comment #7.
https://bugzilla.novell.com/show_bug.cgi?id=495224 -- 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.
participants (1)
-
bugzilla_noreply@novell.com