From: Tomasz Chmielewski <mangoo@wpkg.org>
Subject: Re: how to check if file locking is working?
Date: Thu, 26 Apr 2007 14:19:20 +0200
Message-ID: <463098C8.8010900@wpkg.org>
References: <46308D00.5040109@wpkg.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: nfs@lists.sourceforge.net
In-Reply-To: <46308D00.5040109@wpkg.org>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

Tomasz Chmielewski wrote:
> How can I check if file locking is working?
> 
> I have a NFS4 server (Linux x86) and a NFS4 client (Linux ARM).
> 
> 
> NFS4 server exports a Debian-ARM root filesystem (/bin, /etc, /usr... a 
> complete OS).
> 
> I want to "upgrade" the Debian-ARM root filesystem in a NFS4 chroot, but 
> it fails - dpkg claims that:
> 
> debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
> another process
> 
> It's not true, as that export is only used by that one client.
> 
> So what comes to my mind, is that file locking is somehow broken.
> 
> How can I check if NFS4 file locking works properly, or is broken?

I changed the client to use NFSv3 instead of NFSv4, and suddenly, the 
things started to work...

Ideas what I might be missing? Why locking works if I use NFSv3 on the 
client, but doesn't when I use NFSv4 on the client (other than NFS 
version, nothing else changed).

Kernel option on a client or server, export options on the server, mount 
options on the client etc.?


-- 
Tomasz Chmielewski
http://wpkg.org


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs