Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 3 Apr 2002 21:57:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 3 Apr 2002 21:57:03 -0500 Received: from tmr-02.dsl.thebiz.net ([216.238.38.204]:1540 "EHLO gatekeeper.tmr.com") by vger.kernel.org with ESMTP id ; Wed, 3 Apr 2002 21:56:50 -0500 Date: Wed, 3 Apr 2002 21:54:30 -0500 (EST) From: Bill Davidsen To: Andreas Dilger cc: Jauder Ho , Linux-Kernel Mailing List Subject: Re: Ext2 vs. ext3 recovery after crash In-Reply-To: <20020403102550.GT4735@turbolinux.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Apr 2002, Andreas Dilger wrote: > Well, 'mount' output is useless w.r.t. the root filesystem, because it is > simply copied from /etc/fstab. You need to check /proc/mounts to see if > it is _ever_ being mounted as ext3 (lots of people have this problem, > especially if they use initrds and ext3 as a module). The problem is that the initial mount is changing. I was at one point making ext3 a module, and building initrd files with the ext3 modules and fstab in the initrd. Didn't seem the way to go so I put ext3 in the kernel, and that (usually) works. So I'm not making that particular error. Thanks for the ideas, I'm going to collect dmesg output and post so someone can tell me I missed something obvious. Unless someone has a way to so it from crashing, in which case I'll duck the problem for the moment. -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - 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/