[Bug 13992] New: ext3 data=ordered in fstab prevents booting

[Bug 13992] New: ext3 data=ordered in fstab prevents booting

[bugzilla-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=13992

           Summary: ext3 data=ordered in fstab prevents booting
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.30.4
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@kernel-bugs.osdl.org
        ReportedBy: rogerx@sdf.lonestar.org
        Regression: No


I ran into a problem when, when setting CONFIG_EXT3_DEFAULTS_TO_ORDERED=n, the
system will not complete booting when data=ordered is set on the root
filesystem within /etc/fstab.

(Can't remember the exact debug output as I've been muddling over possible
e100.c system freezes.)


Some work quick hacks that may help resolve are, fsck the filesystem and
removing the filesystem option from the /etc/fstab file.


This will likely occur with people upgrading from 2.6.29 to 2.6.30 with the
data=ordered filesystem option set in fstab.

(I personally like a more stable filesystem, so I've set
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y due a more severe bug I was tracking down in
2.6.30 concerning e100.c)

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 13992] ext3 data=ordered in fstab prevents booting

[bugzilla-daemon]

http://bugzilla.kernel.org/show_bug.cgi?id=13992


Jan Kara <jack@suse.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jack@suse.cz
         AssignedTo|fs_ext3@kernel-bugs.osdl.or |jack@suse.cz
                   |g                           |




--- Comment #1 from Jan Kara <jack@suse.cz>  2009-08-19 12:46:59 ---
Oh, I see what's the problem: You cannot change journalling mode on remount. So
if by default a filesystem gets mounted as data=writeback, then mount
remounting the fs rw fails because it specifies data=ordered from /etc/fstab.
Sorry, this is a userspace issue - either you have to specify
rootflags=data=ordered or you should use initrd and initially mount the
filesystem with proper options.

I understand this might be nasty to users but there's no better solution...

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.