Bug#520009: ext3 'data=foo' on root fs is broken
[maximilian attems] if you change fstab you have to also pass the corresponding bootflag. if you have manualy set this, you just have to fix your bootloader. if debian installer sets it which i don't know, then it is up to debian installer to pass the right rootflags. Changing fstab has no effect ? I ever wondered how the mount option of root in /etc/fstab relates to the kernel-bootflag. There should be a hint written as a comment in /etc/fstab that some mount options modifying the rootfs only have an effect via bootflag or initrd ! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520009: ext3 'data=foo' on root fs is broken
[Ralph] There should be a hint written as a comment in /etc/fstab that some mount options modifying the rootfs only have an effect via bootflag or initrd ! For most flags, it does not matter. The initrd mounts the root filesystem read-only, but early in the boot process, an init script runs something like 'mount -o remount,rw /', and 'mount' reads /etc/fstab and calls the kernel with all the right flags. The reason this doesn't work for 'data=' is because of a restriction in the kernel ext3 driver, where you cannot change your 'data=' parameter in a 'remount'. This leaves you with a read-only system at boot time, because the remount,rw fails. It is also a bit tricky to fix, given that 'mount -o remount' always reads /etc/fstab, which you cannot edit until your filesystem is read-write. (On the machine in question, I'm just glad I had a serial console through a Portmaster, since it was unable to start sshd.) -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ signature.asc Description: Digital signature
Bug#520009: ext3 'data=foo' on root fs is broken
On Fri, Mar 27, 2009 at 04:21:21PM +0100, Ralph wrote: [maximilian attems] if you change fstab you have to also pass the corresponding bootflag. if you have manualy set this, you just have to fix your bootloader. if debian installer sets it which i don't know, then it is up to debian installer to pass the right rootflags. Changing fstab has no effect ? yes. NEWS at 11. I ever wondered how the mount option of root in /etc/fstab relates to the kernel-bootflag. There should be a hint written as a comment in /etc/fstab that some mount options modifying the rootfs only have an effect via bootflag or initrd ! change your rootdev and you have to update your root cmdline bootarg. for asistance ask on a debian user malinglist. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520009: ext3 'data=foo' on root fs is broken
On Wed, 18 Mar 2009, Peter Samuelson wrote: So, if I understand you correctly, the reason you can't fix this is because you have no desire to support a configuration that was not produced by debian-installer? well your usage falls under advanced messing with your box, so i'd expect such a user to be able to read man initramfs-tools to find the corresponding bootflag. By this same logic, it seems to me that debian-installer should also set 'rootfstype' on the kernel command line, so that the initramfs does not have to detect that either. no the logic is not the same. the fstype can be probed in a generic way whereas you are asking for a hardcoding for a special box. the fstype can be probed as the corresponding root bootarg is passed to initramfs and yes d-i takes care of that one. kind regards -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520009: ext3 'data=foo' on root fs is broken
On Tue, 17 Mar 2009, Peter Samuelson wrote: initramfs-tools should not pick up data= from /etc/fstab, but it does not. [maximilian attems] too many negations in one line, what are you trying to say? Yes, I meant to say: initramfs-tools should pick up data= from /etc/fstab, but it does not. no sorry, we can't. if you change fstab you have to also pass the corresponding bootflag. if you have manualy set this, you just have to fix your bootloader. if debian installer sets it which i don't know, then it is up to debian installer to pass the right rootflags. thus not closing away but ccing debian-installer guys. 12:49 maks can d-i set the data=ordered ext3 mountflag ? 12:53 cjwatson I don't think it can set it at the moment this would then be a wishlist on partman or such to allow to set this ext3 param. kind regards -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520009: ext3 'data=foo' on root fs is broken
On Mon, 16 Mar 2009, Peter Samuelson wrote: However, it also has a restriction that you cannot change the 'data=' parameter with 'remount'. Therefore, you have to pass the correct one at initial mount time, even though the data= parameter does not directly affect a read-only fs. If you don't specify, you get data=ordered. initramfs-tools should not pick up data= from /etc/fstab, but it does not. too many negations in one line, what are you trying to say? The workaround is 'rootflags=data=foo' on the kernel command line. how is rootflags an workaround that has always been the correspondent bootparam? The consequence is that the root fs cannot be remounted rw: EXT3-fs: cannot change data mode on remount mount: / not mounted already, or bad option are you saying that rootflags, doesn't work!?? -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520009: ext3 'data=foo' on root fs is broken
initramfs-tools should not pick up data= from /etc/fstab, but it does not. [maximilian attems] too many negations in one line, what are you trying to say? Yes, I meant to say: initramfs-tools should pick up data= from /etc/fstab, but it does not. The workaround is 'rootflags=data=foo' on the kernel command line. how is rootflags an workaround that has always been the correspondent bootparam? It is a workaround, because it causes the system to boot normally, i.e., it successfully works around the problem that the initramfs does not pass the correct mount option. The consequence is that the root fs cannot be remounted rw: EXT3-fs: cannot change data mode on remount mount: / not mounted already, or bad option are you saying that rootflags, doesn't work!?? No, sorry, I meant: this is the consequence of the bug, if you do not apply the workaround (to menu.lst or whatever). -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520009: ext3 'data=foo' on root fs is broken
Package: initramfs-tools
Version: 0.92o
Severity: normal
ext3 includes mount option 'data={ordered,writeback,journal}'.
However, it also has a restriction that you cannot change the 'data='
parameter with 'remount'. Therefore, you have to pass the correct one
at initial mount time, even though the data= parameter does not
directly affect a read-only fs. If you don't specify, you get
data=ordered.
initramfs-tools should not pick up data= from /etc/fstab, but it does
not. The workaround is 'rootflags=data=foo' on the kernel command
line.
The consequence is that the root fs cannot be remounted rw:
EXT3-fs: cannot change data mode on remount
mount: / not mounted already, or bad option
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to bash
Versions of packages initramfs-tools depends on:
ii cpio2.9-13 GNU cpio -- a program to manage archives of
ii findutils 4.4.0-2 utilities for finding files--find, xargs
ii klibc-utils 1.5.12-2small utilities built with klibc for early
ii module-init-tools 3.4-1 tools for managing Linux kernel modules
ii udev0.125-7 /dev/ and hotplug management daemon
Versions of packages initramfs-tools recommends:
ii busybox 1:1.10.2-2 Tiny utilities for small and embedded syste
initramfs-tools suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
