From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brian May <brian@vpac.org>
Subject: Re: open sleeps
Date: Fri, 20 Jun 2008 10:07:26 +1000
Message-ID: <485AF4BE.6090409@vpac.org>
References: <485AE866.6070206@vpac.org> <20080620095813.22fb518e.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 <sfr@canb.auug.org.au>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from zimbra.vpac.org ([202.158.218.6]:43140 "EHLO zimbra.vpac.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754016AbYFTAHa (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 19 Jun 2008 20:07:30 -0400
In-Reply-To: <20080620095813.22fb518e.sfr@canb.auug.org.au>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Stephen Rothwell wrote:
> So, it would seem some other process has taken write leases on your
> files but does not release them in a timely manner.  You can see the
> current leases in /proc/locks.
>   
What is a lease? Is this a kernel level thing or user level thing?

What is the format of /proc/locks? I assume the 4th field is PID, what 
is the next field? How do I work out what is locked?

Thanks.

Brian May