Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Feb 2003 17:26:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Feb 2003 17:26:01 -0500 Received: from ip68-13-105-80.om.om.cox.net ([68.13.105.80]:2688 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id ; Thu, 6 Feb 2003 17:26:00 -0500 Date: Thu, 6 Feb 2003 16:35:43 -0600 (CST) From: Thomas Molina X-X-Sender: tmolina@localhost.localdomain To: Andreas Dilger cc: Andrew Morton , Subject: Re: possible partition corruption In-Reply-To: <20030206141415.J18636@schatzie.adilger.int> 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 Content-Length: 1035 Lines: 25 On Thu, 6 Feb 2003, Andreas Dilger wrote: > On Feb 06, 2003 15:05 -0600, Thomas Molina wrote: > > On Thu, 6 Feb 2003, Andrew Morton wrote: > > > Everything you describe is consistent with a kernel which does not have ext3 > > > compiled into it. > > > > > > That is an ext3 filesystem in the "needs journal recovery" state. ext2 > > > cannot mount that until either fsck or the ext3 kernel driver has run > > > recovery. > > > > I'm aware of that. I attached the config file showing ext3 was compiled > > in. I went through several iterations to ensure that having the proper > > filesystem compiled in was done. > > Maybe some config/linking breakage puts ext2 in front of ext3 in the probe > order? Try compiling with ext2 as a module. Nope. I still got the same symptoms. - 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/