From: "J. Bruce Fields" Subject: Re: NFS client hang on attempt to do async blocking posix lock enqueue Date: Fri, 18 Jan 2008 18:07:34 -0500 Message-ID: <20080118230734.GE9754@fieldses.org> References: <20071129191532.GB17907@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, Manoj Naik , Oleg Drokin To: Marc Eshel Return-path: Received: from mail.fieldses.org ([66.93.2.214]:54206 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757481AbYARXHh (ORCPT ); Fri, 18 Jan 2008 18:07:37 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Nov 29, 2007 at 02:41:57PM -0800, Marc Eshel wrote: > The problem seems to be with the fact that the client and server are on > the same machine. This test work fine with or without an underlaying fs > that supports locking when the client and the server are on a different > machines. Like you said the server is trying to send the grant message to > the client but for some reason it fails when the client is on the same > machine. That *shouldn't* make a difference, so we need to take another look at this--Oleg, this problem is still unfixed, right? --b. > Marc. > > "J. Bruce Fields" wrote on 11/29/2007 11:15:32 AM: > > > On Thu, Nov 29, 2007 at 02:04:40PM -0500, Oleg Drokin wrote: > > > Hello! > > > > > > There is a problem with blocking async posix lock enqueue in > > > 2.6.22 and 2.6.23 kernels. Lock call to underlying FS is done > > > just fine, but when fl_grant is called to inform lockd of > > > succesful granting, nothing happens, and no reply to client is > > > sent. The end result is client reports that the server is not > > > responding. I enabled dprintks in the code and I see that > > > immediately after fl_grant, there is nlmsvc_grant_blocked message > > > (after callback: label) printed. Then server not responding > > > messages start, and after every message about "coulndn't create > > > RPC handle for localhost" I see nlmsvc_grant_blocked "lockd: > > > GRANTing blocked lock" message again with no activity from > > > underlying FS. > > > > > > I am attaching a reproducer that I have, it is quite simple > > > actually. Take note, that path to file to lock is hardcoded, so > > > adjust for your environment please. Lcoking should be performed > > > on a file that resides on nfs client mountpoint. > > > > > > I reproduced the problem with 2.6.22 and 2.6.23 with Lustre (I am > > > working on adapting lustre to async posix locks API) and GFS2. > > > Setup is totally local, i.e. I have single node on which there is > > > gfs (both server and client) (or lustre - just client, but that > > > does not make any difference), nfs server and nfs client that > > > mounts exported gfs or lustre. > > > > Thanks, I'll take a look. Replying now just to add Marc to the cc:. > > > > --b. >