Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Feb 2004 16:33:30 -0800 (PST)
Received: from zok.sgi.com (mtvcafw.SGI.COM [192.48.171.6])
	by oss.sgi.com (8.12.10/8.12.9) with SMTP id i1Q0XHKO020632
	for <linux-xfs@oss.sgi.com>; Wed, 25 Feb 2004 16:33:17 -0800
Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135])
	by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id i1Q0XCF6021560
	for <linux-xfs@oss.sgi.com>; Wed, 25 Feb 2004 16:33:12 -0800
Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207])
	by flecktone.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id i1Q0XBj334618593;
	Wed, 25 Feb 2004 18:33:11 -0600 (CST)
Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id i1Q0WtEr409212; Wed, 25 Feb 2004 18:33:05 -0600 (CST)
Date: Wed, 25 Feb 2004 18:32:55 -0600 (CST)
From: Eric Sandeen <sandeen@sgi.com>
X-X-Sender: sandeen@stout.americas.sgi.com
To: Jason White <jasonw@ariel.ucs.unimelb.edu.au>
cc: linux-xfs <linux-xfs@oss.sgi.com>
Subject: Re: XFS problem: system hang during shutdown; corruption reported 
  by xfs_check
In-Reply-To: <16445.14412.723115.815734@jdc.local>
Message-ID: <Pine.LNX.4.44.0402251830100.31642-100000@stout.americas.sgi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-archive-position: 2238
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: sandeen@sgi.com
Precedence: bulk
X-list: linux-xfs

On Thu, 26 Feb 2004, Jason White wrote:

> Eric Sandeen writes:
>  > It looks like the filesystem is not in bad shape;
>  > ideally make sure it's been cleanly unmounted, then
>  > point a recent xfs_repair at it.  Running that
>  > under an old kernel should not be a problem.
> 
> Thanks.
> Repair fixed the disconnected inode, and that was it (the file in
> /lost+found turned out to be empty).
> 
> Is there any test you would like to be run if the system hangs again
> durning unmount? I expect to upgrade tis kernel before too long.

if you have kdb in place, enter kdb and backtrace the hung process,
that would be a hint.  

kdb> ps
kdb> btp <process id>

If no kdb, sysrq-t should dump all task info as well.

> Thank you once again for the help.
> Jason.

No problem!

-eric