Messages in this thread | | | From | Keith Owens <> | Subject | Re: 2.4.20-rc1 dirty ext2 mount error | Date | Wed, 06 Nov 2002 21:43:49 +1100 |
| |
On Wed, 6 Nov 2002 01:41:43 -0700, Andreas Dilger <adilger@clusterfs.com> 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 (bhcompile@stripples.devel.redhat.com) (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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |