xfs
[Top] [All Lists]

Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD)

To: Steve Lord <lord@xxxxxxx>
Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD)
From: Chris Wedgwood <cw@xxxxxxxx>
Date: Thu, 19 May 2005 14:35:22 -0700
Cc: Joshua Baker-LePain <jlb17@xxxxxxxx>, Lee Revell <rlrevell@xxxxxxxxxxx>, Gregory Brauer <greg@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx, Jakob Oestergaard <jakob@xxxxxxxxxxxxx>
In-reply-to: <428D0540.4000107@xfs.org>
References: <428B7D7F.9000107@wildbrain.com> <20050518175925.GA22738@taniwha.stupidest.org> <20050518195251.GY422@unthought.net> <Pine.LNX.4.58.0505181556410.6834@chaos.egr.duke.edu> <428BA8E4.2040108@wildbrain.com> <Pine.LNX.4.58.0505191537560.7094@chaos.egr.duke.edu> <Pine.LNX.4.58.0505191650580.7094@chaos.egr.duke.edu> <1116536963.23186.2.camel@mindpipe> <Pine.LNX.4.58.0505191713540.7094@chaos.egr.duke.edu> <428D0540.4000107@xfs.org>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Thu, May 19, 2005 at 04:29:36PM -0500, Steve Lord wrote:
> Joshua Baker-LePain wrote:

> Does xfs_repair report anything after this has happened, it looks
> like it is trying to read a directory block up from disk to satisfy
> a lookup request and failing for some reason.

bit corruption?  bad hardware maybe?


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