xfs
[Top] [All Lists]

Re: xfs_repair hung...safe to terminate?

To: Jon Lewis <jlewis@xxxxxxxxx>
Subject: Re: xfs_repair hung...safe to terminate?
From: Nathan Scott <nathans@xxxxxxx>
Date: Fri, 17 Jun 2005 10:09:53 +1000
Cc: Net Llama! <netllama@xxxxxxxxxxxxx>, linux-xfs <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.58.0506161045460.21993@xxxxxxxxxxxxxxx>; from jlewis@xxxxxxxxx on Thu, Jun 16, 2005 at 10:53:49AM -0400
References: <Pine.LNX.4.58.0506152011310.21993@xxxxxxxxxxxxxxx> <Pine.LNX.4.58.0506160950230.21993@xxxxxxxxxxxxxxx> <Pine.LNX.4.58.0506160835510.13228@xxxxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0506161045460.21993@xxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Thu, Jun 16, 2005 at 10:53:49AM -0400, Jon Lewis wrote:
> It's an old server.  I'm willing to try (have already compiled) 2.4.31
> (unmodified source from kernel.org), but from some searches of the archive
> and SGI's bugzilla, this looks like a long standing unresolved bug
> affecting xfs in both 2.4 and 2.6 kernels.  At this point, I'm mostly
> curious if anyone has any ideas for solutions/workarounds, or if it's time
> to simply abandon use of XFS.

Upgrading your kernel is your best bet.  CVS on oss.sgi.com is
always very stable these days, and kernel.org always lags it
slightly (of course) so I'd recommend using CVS.

There were a series of xfs_iget related races that Christoph
plugged several months ago.  Most, if not all, of these are now
resolved - we have one/two reports of people running stress for
several days and then finally tripping over this issue, but we
have been unable to reproduce that problem so far.

cheers.

-- 
Nathan


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