[Bug 445189] New: boot.rootfsck doesn't remount root rw
https://bugzilla.novell.com/show_bug.cgi?id=445189 Summary: boot.rootfsck doesn't remount root rw Product: openSUSE 11.1 Version: Factory Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jslaby@novell.com QAContact: qa@suse.de Found By: --- When on battery or fastboot is set, root partition is not remounted rw. This causes the rest of system to not boot -- each service fails with read-only filesystem error. -- 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=445189
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c1
--- Comment #1 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=445189
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=445189
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=445189
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c2
--- Comment #2 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=445189
User ro@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c3
Ruediger Oertel
https://bugzilla.novell.com/show_bug.cgi?id=445189
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c4
--- Comment #4 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=445189
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c5
--- Comment #5 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=445189
User ro@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c6
Ruediger Oertel
https://bugzilla.novell.com/show_bug.cgi?id=445189
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c7
--- Comment #7 from Jiri Slaby
There are a lot of flags used on the kernels command line which are only used in user space (e.g. `confirm'), there are parameters for both the kernel and the user space, and at last but not least there are flags which belongs to the kernel only. The flag `ro' IMHO belongs to both the kernel and the user space ... e.g. I use this flag mostly combinded for booting into single user mode.
The other most used distros doesn't share your opinion. Fedora adds readonlyroot boot parameter, debian doesn't add anything and mounts rw unconditionaly unless you specify ro in fstab.
Beside this not using initrd will force the file system check of the root file system done by boot.rootfsck,
Well, no. I repeat that this happens unless fastboot is specified or being on battery. I can't see a path in the code which would do this in these particular cases.
that is that this scripts is readed from the same partition which is checked. Normally this should be done by the initrd.
Initrd slows down boot significantly and many users simply doesn't use it. Even boot scripts count with this, except this bug. (Beside the fact I haven't tested this situation with initrd, so that I can't verify or refute if it is remounted rw.) -- 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=445189
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c8
--- Comment #8 from Jiri Slaby
the main question is: should "ro" on the boot commandline end up with "/" mounted "ro" or "rw" after booting is finished ?
Whatever Thorsten utters as a fact from now on, it'll still remain a bug if I pass nothing on the commandline. Kernel defaults to ro and nobody will remount it rw in that case anyway. -- 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=445189
User kukuk@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c9
Thorsten Kukuk
any thoughts from your side Thorsten ?
the main question is: should "ro" on the boot commandline end up with "/" mounted "ro" or "rw" after booting is finished ?
We had this discussion already some month ago. "ro" is a pure kernel option and does not overwrite /etc/fstab. We fixed that bug already for the case the fsck is running, so seems we need to fix it for the case that fsck is not running. meand, if fstab says "ro", don't mount it rw, else mount it rw. -- 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=445189
User jslaby@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c10
--- Comment #10 from Jiri Slaby
meand, if fstab says "ro", don't mount it rw, else mount it rw.
Seems OK to me. I'll also appreciate fedora's readonlyroot parameter as mentioned in comment #7. Should I create a new "enhancement bug" for this, or does the parameter look like a nonsense in your eyes? -- 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=445189
Ruediger Oertel
https://bugzilla.novell.com/show_bug.cgi?id=445189
Martin Mrazik
https://bugzilla.novell.com/show_bug.cgi?id=445189
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=445189
User ro@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=445189#c11
Ruediger Oertel
participants (1)
-
bugzilla_noreply@novell.com