From: ms419@freezone.co.uk
Subject: F_SETLK failed, file already locked by pid 0
Date: Sun, 22 Aug 2004 15:50:19 -0700
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <A4B2A13E-F48D-11D8-A02C-000A95C71776@freezone.co.uk>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: nfs@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

I suspect locking isn't working:

F_SETLK failed, file already locked by pid 0

I encounter this error with a user mode linux root image on an NFS 
mount, but not with an image on a local file system. An image on an NFS 
mount should work, provided locking works.

The NFS client is running NFS 1.0.6 & a custom 2.6.7 kernel. The NFS 
server is running NFS kernel server 1.0.6 & a custom 2.4.27 kernel. 
Everything I've read claims that locking is now implemented in the 
linux NFS kernel server. A lockd process is running on both the client 
& the server. According to all the documentation I've read, locking 
should be working; what am I missing? Pointers to diagnostic 
information, configuration, & documentation much appreciated!

Why isn't locking working?

Thanks,

Jack


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs