[Bug 631300] New: param 'logbsize=256k' seen as illegal in ramdisk kernel for 'xfs' /etc/fstab option -- BUG
http://bugzilla.novell.com/show_bug.cgi?id=631300 http://bugzilla.novell.com/show_bug.cgi?id=631300#c0 Summary: param 'logbsize=256k' seen as illegal in ramdisk kernel for 'xfs' /etc/fstab option -- BUG Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse@tlinx.org QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 logbsize=256k forces a boot-ramdisk created during an 11.2->11.3 upgrade not to boot. I have to mount that param by hand without that parameter, and the mount will continue. Fixing it on the real disk doesn't fix anything -- as it also WORKS when it is booted up under the real kernel. So why is it broken on the boot system included for the RAM DISK? This makes a good case including needed drivers in a kernel build and booting from disk. Note -- the logbsize param works in 11.2 and 11.3 -- just not in the ramdisk boot image created during the upgrade (I don't know about later -- haven't created any more images for the upgrade computer). Reproducible: Always Steps to Reproduce: 1. use xfs fs. for all 2. use logbsize=256k as option for all file systems 3. upgrade from 11.2 -> 11.3 -- end up with non working ramdisk image. Actual Results: system won't boot without manually mounting the root file system. Expected Results: booting normally. -- 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=631300 http://bugzilla.novell.com/show_bug.cgi?id=631300#c yang xiaoyu <xyyang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyyang@novell.com AssignedTo|bnc-team-screening@forge.pr |locilka@novell.com |ovo.novell.com | -- 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=631300 http://bugzilla.novell.com/show_bug.cgi?id=631300#c Lukas Ocilka <locilka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juhliarik@novell.com Component|Installation |Kernel AssignedTo|locilka@novell.com |kernel-maintainers@forge.pr | |ovo.novell.com QAContact|jsrain@novell.com |qa@suse.de -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=631300 https://bugzilla.novell.com/show_bug.cgi?id=631300#c1 Greg Kroah-Hartman <gregkh@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |suse@tlinx.org --- Comment #1 from Greg Kroah-Hartman <gregkh@suse.com> 2011-08-31 20:09:49 UTC --- Is this still an issue on 11.4? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=631300 https://bugzilla.novell.com/show_bug.cgi?id=631300#c2 L. A. Walsh <suse@tlinx.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|suse@tlinx.org | --- Comment #2 from L. A. Walsh <suse@tlinx.org> 2011-08-31 14:14:17 PDT --- I'd say the last comment is still valid. "I don't know about what ram disk boot images' it might be creating now, as I moved away from using a ramdisk for booting. It made booting more complicated, so when I needed to examine things at hardware initialization (was trying to get a serial console to work at the time), by the time it got to 'my init' on disk, all the initial state had been set & reset by the ramdisk boot that then loaded my main sys. After that and the problems with it not mounting my disks, I've not tried again. So...If no one else is complaining...I'd say close it -- it's not bothering me at this point. If I find it again in the future, I can reopen it... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=631300 https://bugzilla.novell.com/show_bug.cgi?id=631300#c3 Greg Kroah-Hartman <gregkh@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #3 from Greg Kroah-Hartman <gregkh@suse.com> 2011-08-31 21:19:50 UTC --- Thanks, will close out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=631300 https://bugzilla.novell.com/show_bug.cgi?id=631300#c4 --- Comment #4 from L. A. Walsh <suse@tlinx.org> 2011-08-31 15:09:20 PDT --- Dang... the novell DB doesn't have a 'Unable to reproduce' resolution -- only a 'works for me'... Couldn't really resolve this as 'works for me', as it's not easily testable, but 'unable to reproduce' would likely have been a closer resolution if it had been available... but .. eh! it's not!.. ;-) -- Configure bugmail: https://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