xfs
[Top] [All Lists]

Re: Irreparable 'corrupt dinode ... error 990' Revisited

To: Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx>
Subject: Re: Irreparable 'corrupt dinode ... error 990' Revisited
From: Federico Sevilla III <jijo@xxxxxxxxxxx>
Date: Thu, 5 Aug 2004 00:40:37 +0800
In-reply-to: <20040804153356.GD26826@xxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx>
References: <20040804153356.GD26826@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040523i
On Wed, Aug 04, 2004 at 11:33:56PM +0800, Federico Sevilla III wrote:
> The problem was triggered by, I believe, the hard system lockup caused
> by some problem with my external USB hard drive enclosure (accessed
> via usb-storage, it's essentially a USB to IDE controller/converter
> with a case). I don't know how to reproduce the lockup itself, however
> during both instances that this lockup happened I got filesystem
> corruption after that xfs_repair could not repair.
> 
> I would have understood filesystem corruption in the filesystem stored
> on the external storage. Unfortunately, I had filesystem corruption in
> my root filesystem, which is /dev/hda1.

I just mounted, unmounted, then did an xfs_repair of my filesystem in
the external storage, and it did NOT have any corruption despite the
fact that I was doing file operations on it when the lockup occured.
Strange! The root filesystem goes bork (on an otherwise idle inode), but
the active filesystem on the device that causes the crash (I think it
causes it anyway) is a-okay.

 --> Jijo

-- 
Federico Sevilla III : jijo.free.net.ph : When we speak of free software
GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price.


rom owner-linux-xfs Wed Aug  4 10:36:59 2004
Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Aug 2004 10:37:05 
-0700 (PDT)
Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77])
        by oss.sgi.com (8.13.0/8.13.0) with ESMTP id i74HawaS002446
        for <linux-xfs@xxxxxxxxxxx>; Wed, 4 Aug 2004 10:36:58 -0700
Received: from taniwha.stupidest.org 
(adsl-63-202-172-176.dsl.snfc21.pacbell.net [63.202.172.176])
        by pimout1-ext.prodigy.net (8.12.10 milter /8.12.10) with ESMTP id 
i74Har5C132454
        for <linux-xfs@xxxxxxxxxxx>; Wed, 4 Aug 2004 13:36:53 -0400
Received: by taniwha.stupidest.org (Postfix, from userid 38689)
        id DDA74115C868; Wed,  4 Aug 2004 10:36:51 -0700 (PDT)
Date: Wed, 4 Aug 2004 10:36:51 -0700
From: Chris Wedgwood <cw@xxxxxxxx>
To: Linux-XFS Mailing List <linux-xfs@xxxxxxxxxxx>
Subject: Re: Irreparable 'corrupt dinode ... error 990' Revisited
Message-ID: <20040804173651.GA1107@xxxxxxxxxxxxxxxxxxxxx>
References: <20040804153356.GD26826@xxxxxxxxxxxxxxxxxxxx> 
<20040804164037.GC18867@xxxxxxxxxxxxxxxxxxxx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040804164037.GC18867@xxxxxxxxxxxxxxxxxxxx>
X-archive-position: 3838
X-ecartis-version: Ecartis v1.0.0
Sender: linux-xfs-bounce@xxxxxxxxxxx
Errors-to: linux-xfs-bounce@xxxxxxxxxxx
X-original-sender: cw@xxxxxxxx
Precedence: bulk
X-list: linux-xfs

On Thu, Aug 05, 2004 at 12:40:37AM +0800, Federico Sevilla III wrote:

> I just mounted, unmounted, then did an xfs_repair of my filesystem
> in the external storage, and it did NOT have any corruption despite
> the fact that I was doing file operations on it when the lockup
> occured.

Could be an in-memory corruption.  Do you have ECC memory?


  --cw


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