From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: file leases Date: Tue, 21 Sep 2004 09:40:08 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040921084008.GG28786@mail.shareable.org> References: <20040920202733.GF28786@mail.shareable.org> <20040920203430.6D5761BBA3@citi.umich.edu> <20040921132152.7f6a54af.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "William A.(Andy) Adamson" , linux-fsdevel@vger.kernel.org Return-path: Received: from mail.shareable.org ([81.29.64.88]:55508 "EHLO mail.shareable.org") by vger.kernel.org with ESMTP id S267522AbUIUIk3 (ORCPT ); Tue, 21 Sep 2004 04:40:29 -0400 To: Stephen Rothwell Content-Disposition: inline In-Reply-To: <20040921132152.7f6a54af.sfr@canb.auug.org.au> List-Id: linux-fsdevel.vger.kernel.org Stephen Rothwell wrote: > > > When I share a directory using Samba 3.0.6, sometimes local access to > > > a file stalls for a while - on the order of 10 seconds to open a file. > > > > if your open() is blocking (did not specify O_NONBLOCK) then > > break_lease will contact all other processes (samba clients) one > > at a time, and will not return until all have been contacted. this > > could take a while. > > And, of course, the samba servers may have to contact their clients and > get them to release their oplocks ... Quite, but the client is a Windows 2000 box completely idle with nothing holding the file open, and a good LAN connection. If an idle client won't release oplocks quickly on request, then there's a problem. Surely people using lots of Windows clients don't have to wait 10 seconds or more to open a file which somebody else had open recently on a different box? I suspect a Samba problem but anyways the answer is to disable oplocks. It _could_ be a fault in leases, which is why I asked if they're known to be working. -- Jamie