Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 20 May 2003 22:11:58 -0700 (PDT) Received: from skarpsey.home.lan (12-207-41-15.client.attbi.com [12.207.41.15]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h4L5BD2x000854 for ; Tue, 20 May 2003 22:11:13 -0700 Received: from valhalla.home.lan (valhalla.home.lan [192.168.0.2]) by skarpsey.home.lan (8.12.9/8.12.9) with ESMTP id h4L5Akx2024495 for ; Wed, 21 May 2003 00:10:46 -0500 From: Kelledin To: linux-xfs@oss.sgi.com Subject: RESOLVED - xfs deadlocks on alpha Date: Wed, 21 May 2003 00:11:09 -0500 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200305210011.09117.kelledin+XFS@skarpsey.dyndns.org> X-archive-position: 4095 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: kelledin+XFS@skarpsey.dyndns.org Precedence: bulk X-list: linux-xfs Content-Length: 727 Lines: 19 Ok, I just did one last thing that seems to have completely cleared up the deadlocks I've been experiencing. I simply re-mkfs'd the affected filesystem, and I haven't had any deadlocks since then. Apparently some latent fs damage got left behind by the bug. So...XFS-CVS (as it stands now) is apparently stable on Alpha. No further patching needed. Those who have been bitten by the bug, however, may need to repair or rebuild the filesystem before the deadlocks go away. xfs_repair by itself may be enough; if I'd been a little less spontaneous in my testing, I'd have tried that first (d'oh!) -- Kelledin "If a server crashes in a server farm and no one pings it, does it still cost four figures to fix?"