From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian May Subject: Re: open sleeps Date: Fri, 20 Jun 2008 10:50:47 +1000 Message-ID: <485AFEE7.5010703@vpac.org> References: <485AE866.6070206@vpac.org> <20080620095813.22fb518e.sfr@canb.auug.org.au> <485AF4BE.6090409@vpac.org> <20080620102003.8dd1270c.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Stephen Rothwell Return-path: Received: from zimbra.vpac.org ([202.158.218.6]:34189 "EHLO zimbra.vpac.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752089AbYFTAuv (ORCPT ); Thu, 19 Jun 2008 20:50:51 -0400 In-Reply-To: <20080620102003.8dd1270c.sfr@canb.auug.org.au> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Stephen Rothwell wrote: > Its what samba calls an oplock. Its like a kernel file lock but it > blocks opens and notifies the holder (who is supposed to clean up and > release the lease). If the lease is not released in 45 seconds (by > default) then the kernel assumes that the holder is broken and breaks the > lease and allows the open to proceed. > Ok, so I guess it is most likely Samba's fault then. Most likely this is the only application that uses leases/oplocks on this computer anyway. I will keep investigating... Thanks. Brian May