Date: Fri, 29 Oct 2004 17:37:23 +1000
From: Nathan Scott <nathans@sgi.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-xfs@oss.sgi.com
Subject: Re: XFS strangeness, xfs_db out of memory
Message-ID: <20041029073723.GH1246@frodo>
References: <200410240857.31893.robin.rosenberg.lists@dewire.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410240857.31893.robin.rosenberg.lists@dewire.com>
User-Agent: Mutt/1.5.3i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 918
Lines: 26

On Sun, Oct 24, 2004 at 08:57:26AM +0200, Robin Rosenberg wrote:
> Hi,
> 
> I was testing a tiny script on top of xfs_fsr to show fragmentation and the 
> resultss of defragmentation.  As a result of fine tuning the output I ran the 
> script repeatedly and suddenly got error from find (unknown error 999 if my 
> memory serves me. It scrolled off the screen).
> ...
> xfs_info $dev
> xfs_db -r $dev -c "frag -v"

This is accessing the device while the filesystem is mounted,
in older kernels (like the one you have) that would cause the
above corruption error in XFS - thats resolved now.

As to the IDE error you saw, I'm not sure how fatal that is.

cheers.

-- 
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/