Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 May 2005 14:36:12 -0700 (PDT) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j4JLa5F3032305 for ; Thu, 19 May 2005 14:36:05 -0700 Received: from pimout4-ext.prodigy.net (pimout4-ext.prodigy.net [207.115.63.98]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j4JLZNeg003127 for ; Thu, 19 May 2005 17:35:23 -0400 X-ORBL: [63.205.185.30] Received: from taniwha.stupidest.org (adsl-63-205-185-30.dsl.snfc21.pacbell.net [63.205.185.30]) by pimout4-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id j4JLZMQg185980; Thu, 19 May 2005 17:35:22 -0400 Received: by taniwha.stupidest.org (Postfix, from userid 38689) id B019F528F22; Thu, 19 May 2005 14:35:22 -0700 (PDT) Date: Thu, 19 May 2005 14:35:22 -0700 From: Chris Wedgwood To: Steve Lord Cc: Joshua Baker-LePain , Lee Revell , Gregory Brauer , linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com, Jakob Oestergaard Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD) Message-ID: References: <428B7D7F.9000107@wildbrain.com> <20050518175925.GA22738@taniwha.stupidest.org> <20050518195251.GY422@unthought.net> <428BA8E4.2040108@wildbrain.com> <1116536963.23186.2.camel@mindpipe> <428D0540.4000107@xfs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <428D0540.4000107@xfs.org> X-archive-position: 5276 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: cw@f00f.org Precedence: bulk X-list: linux-xfs Content-Length: 315 Lines: 9 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?