Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933695AbXKOWCS (ORCPT ); Thu, 15 Nov 2007 17:02:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759439AbXKOWCJ (ORCPT ); Thu, 15 Nov 2007 17:02:09 -0500 Received: from ns2.g-housing.de ([81.169.133.75]:52937 "EHLO mail.g-house.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757373AbXKOWCI (ORCPT ); Thu, 15 Nov 2007 17:02:08 -0500 Date: Thu, 15 Nov 2007 23:01:56 +0100 (CET) From: Christian Kujau X-X-Sender: evil@sheep.housecafe.de To: LKML cc: "J. Bruce Fields" , Benny Halevy , Chris Wedgwood , linux-xfs@oss.sgi.com Subject: Re: 2.6.24-rc2 XFS nfsd hang / smbd too In-Reply-To: Message-ID: References: <20071114070400.GA25708@puku.stupidest.org> <473AA72C.6020308@panasas.com> <20071114125907.GB4010@fieldses.org> User-Agent: Alpine 0.99999 (DEB 796 2007-11-08) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 912 Lines: 21 On Thu, 15 Nov 2007, Christian Kujau wrote: > Upon accessing the /data/sub part of the CIFS share, the client hung, waiting > for the server to respond (the [cifs] kernel thread on the client was > spinning, waiting for i/o). On the server, similar things as with the nfsd > processes happened Turns out that the CIFS only hung because the server was already stuck because of the nfsd/XFS issue. After rebooting the server, I was able to access the CIFS shares (the xfs partition too) just fine. Yes, the xfs partition itsself has been checked too and no errors were found. C. -- BOFH excuse #348: We're on Token Ring, and it looks like the token got loose. - 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/