Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Sep 2002 15:21:35 -0700 (PDT)
Received: from UberGeek ([209.184.141.189])
	by oss.sgi.com (8.12.5/8.12.5) with SMTP id g83MLTtG017917
	for <linux-xfs@oss.sgi.com>; Tue, 3 Sep 2002 15:21:29 -0700
Received: (qmail 1885 invoked by uid 500); 3 Sep 2002 22:25:01 -0000
Subject: Re: Kernel Opps/panic with 2.4.19
From: Austin Gonyou <austin@coremetrics.com>
To: Stephen Lord <lord@sgi.com>
Cc: linux-xfs@oss.sgi.com, Andrea Arcangeli <andrea@suse.de>
In-Reply-To: <1031088301.32386.92.camel@UberGeek.coremetrics.com>
References: <1031088301.32386.92.camel@UberGeek.coremetrics.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: Coremetrics, Inc.
Message-Id: <1031091900.32409.101.camel@UberGeek.coremetrics.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.1.0.99 (Preview Release)
Date: 03 Sep 2002 17:25:01 -0500
X-archive-position: 241
X-ecartis-version: Ecartis v1.0.0
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
X-original-sender: austin@coremetrics.com
Precedence: bulk
X-list: linux-xfs

I seemed to have found that after running xfs_repair -L on a fs I knew I
could lose the log for, I can now mount the volume properly. 

Is it because the -RC5-aa1 patch has old XFS code that this is
happening? Should I upgrade my mount to support newer XFS code, and
thusly, log replays?

Please advise. This appears to be the only thing causing any problems on
this system at this point. TIA!


On Tue, 2002-09-03 at 16:25, Austin Gonyou wrote:
> Ok, I guess ksymoops will do that. I only had used it for just plain
> *oopses* before. Sorry about my ignorance. 
> 
> Attatched is the output. 
>  
> -- 
> Austin Gonyou <austin@coremetrics.com>
> Coremetrics, Inc.
> 
>  
-- 
Austin Gonyou <austin@coremetrics.com>
Coremetrics, Inc.