xfs
[Top] [All Lists]

Re: Mount oops from 2.4.20 + xfs-Dec182002

To: Chris Wedgwood <cw@xxxxxxxx>
Subject: Re: Mount oops from 2.4.20 + xfs-Dec182002
From: Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Date: 18 Feb 2003 16:34:37 -0600
Cc: XFS List <linux-xfs@xxxxxxxxxxx>
In-reply-to: <20030218220659.GB15178@f00f.org>
Organization: Coremetrics, Inc.
References: <20030218220659.GB15178@f00f.org>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Tue, 2003-02-18 at 16:06, Chris Wedgwood wrote:
> On Tue, Feb 18, 2003 at 03:56:50PM -0600, Austin Gonyou wrote:
> 
> > >>EIP; c01bdd7e <xfs_ioerror_alert+e/60>   <=====
> 
> Did anything get printed before this oops?   xfs_ioerror_alert should
> print out details of an IO error that looks like it occurred during
> log replay...  I wonder if it was passed a bogus non-zero mp?
> 
> Maybe dumping the log transactions would show if one of the
> transactions is trashed?

Nothing major before this, but the log info looks like this:

Feb 18 14:52:48 Phoenix kernel: XFS mounting filesystem sd(8,128)
Feb 18 14:52:49 Phoenix kernel: Starting XFS recovery on filesystem:
sd(8,128) (dev: 8/128)
Feb 18 14:52:49 Phoenix kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000058
Feb 18 14:52:49 Phoenix kernel:  printing eip:
Feb 18 14:52:49 Phoenix kernel: c01bdd7e
Feb 18 14:52:49 Phoenix kernel: *pde = 36538001
Feb 18 14:52:49 Phoenix kernel: *pte = 00000000
Feb 18 14:52:49 Phoenix kernel: Oops: 0000


> 
>   --cw
-- 
Austin Gonyou <austin@xxxxxxxxxxxxxxx>
Coremetrics, Inc.


<Prev in Thread] Current Thread [Next in Thread>