[lkml]   [2002]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.20-rc1 dirty ext2 mount error
On Wed, 6 Nov 2002 01:41:43 -0700, 
Andreas Dilger <> wrote:
>If you don't simultaneously crash your system running ext3, and then reboot
>into a kernel which does not support ext3 you will be fine. A clean
>shutdown will clear the "needs_recovery" flag (and any ext2-only kernel
>can blissfully use that filesystem), any ext3-aware kernel can also
>mount it again and do a journal flush, or any modern (last year or two)
>e2fsck will clean it up too (from a rescue disk if

You are right, but the 2.4.18 kernel is lying to me.

Linux version 2.4.18-14smp ( (gcc
version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 SMP Wed Sep 4
12:34:47 EDT 2002
has ext2 built in but it boots with initrd containing ext3 as a module.
VFS: Mounted root (ext2 filesystem)
Loading jbd module
Journalled Block Device driver loaded
Loading ext3 module
Mounting root filsystem
EXT3-fs: mounted filesystem with ordered data mode
init starts ...
[/sbin/fsck.ext2 (1) -- /] fsck.ext2 -a /dev/sda1 [PASSED]
Remounting root filesystem in read-write mode: [ OK ]
# mount
/dev/sda1 on / type ext2 (rw)

VFS said that / was ext2, init ran fsck.ext2 against /, fstab says /
whoudl be ext2 and mount claims that it is ext2. Lies! It is still
ext3, the only indication is that lsmod shows a use count of 1 against
ext3. Crashing out of this kernel and into 2.4.20-rc1 which has no
initrd gets the error. And I thought I had got rid of ext3 ...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:30    [W:0.033 / U:7.792 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site