Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Feb 2003 16:23:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Feb 2003 16:23:37 -0500 Received: from ip68-13-105-80.om.om.cox.net ([68.13.105.80]:59776 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id ; Thu, 6 Feb 2003 16:23:36 -0500 Date: Thu, 6 Feb 2003 15:33:19 -0600 (CST) From: Thomas Molina X-X-Sender: tmolina@localhost.localdomain To: Andrew Morton cc: linux-kernel@vger.kernel.org Subject: Re: possible partition corruption In-Reply-To: <20030206132346.4b635676.akpm@digeo.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 Content-Length: 1125 Lines: 28 On Thu, 6 Feb 2003, Andrew Morton wrote: > Thomas Molina wrote: > > > > > Everything you describe is consistent with a kernel which does not have ext3 > > > compiled into it. > > ... > > I'm aware of that. > > In that case you may be experiencing the mysterious vanishing > ext3_read_super-doesn't-work bug. Usually a recompile/relink makes it go > away. I haven't seen it in months. > > Could you please drop this additional debugging in there and see > what happens? I'll try it, but a question did occur to me. I got the hang while booting a freshly-compiled 2.5.59, but the error message was received after supposedly cleaning and recovering the journal. That was using the stock RedHat 8.0 kernel, 2.4.18-24.8.0, which most certainly does have ext3 support. Would the bug you described affect a following boot into a totally different kernel? - 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/