From: Trond Myklebust Subject: Re: read(2) hangs on the client side Date: Sat, 14 May 2005 23:39:57 -0700 Message-ID: <1116139197.12153.3.camel@lade.trondhjem.org> References: <20050508113343.GA629@fox> <1115556864.11308.1.camel@lade.trondhjem.org> <20050508132127.GA1744@fox> <1115560765.11308.6.camel@lade.trondhjem.org> <20050508143754.GA492@fox> <1115635107.24625.0.camel@lade.trondhjem.org> <20050509141339.GA3216@fox> <1115821422.13483.0.camel@lade.trondhjem.org> <20050514223904.GA580@fox> <1116113888.14297.27.camel@lade.trondhjem.org> <20050515062103.GA482@fox> Mime-Version: 1.0 Content-Type: text/plain Cc: nfs@lists.sourceforge.net Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30) id 1DXCnd-0001Av-J6 for nfs@lists.sourceforge.net; Sat, 14 May 2005 23:40:29 -0700 Received: from pat.uio.no ([129.240.130.16] ident=7411) by sc8-sf-mx1.sourceforge.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.41) id 1DXCnQ-0002uq-04 for nfs@lists.sourceforge.net; Sat, 14 May 2005 23:40:29 -0700 Received: from mail-mx3.uio.no ([129.240.10.44]) by pat.uio.no with esmtp (Exim 4.43) id 1DXCnL-0003C5-Lv for nfs@lists.sourceforge.net; Sun, 15 May 2005 08:40:11 +0200 To: Haakon Riiser In-Reply-To: <20050515062103.GA482@fox> Sender: nfs-admin@lists.sourceforge.net Errors-To: nfs-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Post: List-Help: List-Subscribe: , List-Archive: su den 15.05.2005 Klokka 08:21 (+0200) skreiv Haakon Riiser: > I did set 'kernel oplocks = no' globally and restarted Samba, but I > didn't look for locked files with smbstatus. I'll try again and > investigate a little more this time. In the meantime, here's what > smbstatus shows: > > Locked files: > Pid DenyMode Access R/W Oplock Name > -------------------------------------------------------- > 32475 DENY_NONE 0x20089 RDONLY EXCLUSIVE+BATCH foo Sun May 15 08:13:23 2005 > > This lock goes on and off all the time, which probably explains why > this error doesn't happen every single time I try to open the file. > But why does ERR_JUKEBOX cause the client to hang? This lock _is_ > soon released, so shouldn't NFS wake up once that happens? I suspect there were hanging locks. Some of those lease code changes look pretty suspicious, so I think I want to have a chat with Andy & co as soon as I get back to Michigan. In the mean time, please try rebooting the server, and just turn off the lease code using 'sysctl -w fs.leases-enable=0'. Cheers, Trond Cheers, Trond ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs