FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-16-2009, 07:36 PM
Peter Samuelson
 
Default 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 cpio 2.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-2 small utilities built with klibc for early
ii module-init-tools 3.4-1 tools for managing Linux kernel modules
ii udev 0.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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-17-2009, 02:24 PM
maximilian attems
 
Default 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-17-2009, 04:25 PM
Peter Samuelson
 
Default 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-18-2009, 10:57 AM
maximilian attems
 
Default 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-18-2009, 02:51 PM
Peter Samuelson
 
Default Bug#520009: ext3 'data=foo' on root fs is broken

[maximilian attems]
> 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.

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?

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.
--
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 03-19-2009, 09:19 PM
maximilian attems
 
Default 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 08:40 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org