Re: Bug#616317: base: commit= ext3 mount option in fstab has no effect.
Roger Leigh <email@example.com> writes:
> On Thu, May 12, 2011 at 06:31:48PM +0200, Goswin von Brederlow wrote:
>> Adam Borowski <firstname.lastname@example.org> writes:
>> >> Should we try to make this work (at best badly) since a change in
>> >> mount options in /etc/fstab would only take effect at the next
>> >> mkinitramfs and/or update-grub invocation? Or should we just close
>> >> out this bug and say, "tough luck, kid; if you want to change the root
>> >> file system's mount options, you need to edit your kernel's boot
>> >> options using whatever bootloader you might happen to be using"?
>> Or the init scripts could "mount -oremount,commit=300 /". Most options
>> can be altered throught remount. For the few remaining ones
>> (e.g. data=writeback) editing the kernel's boot options is probably ok.
>> The init scripts already do this for read-only / read-write. Why doesn't
>> this work for commit= too?
> The initscripts /do/ already do this. See checkroot.sh and read_fstab
> in /lib/init/mount-functions.sh.
> If it's not working for you, then it's possible that the fstab entry
> for / doesn't match. Might be worth sourcing and running read_fstab
> by hand to see if it's pulling out the options correctly.
Did you ment to send this to email@example.com?