On Fri, 20 Aug 2004, Ara.T.Howard wrote: > > NFS locks can get stale if you have network problems. The server loses the > > client, the lock remains on the server, nobody can lock the file. Everyone > > using NFS eventually runs into this, but good network setup and good kernel > > choices can often mitigate it. > > ours is pretty good but i have that exact situation right now. it's happened > in a peice of code i've designed to try and break nfs locking. it forks > children which get a lock and don't release it, but simply '_exit'. also, the > parent randomly sends SIGKILL to the children after forking them. this loops > as fast as possible on many clients locking the same file. it takes a few > days, but i can create the situation you describe. i've got a stale lock now > that i can see in /proc/locks - and can see the pid of it, but cannot find > this pid on any system. do you know if there is a way to find out which host > the nfs sever thinks the lock is on? i've got a thread going on the nfs list > regarding this > but have gotten no help on the specific issue.
On a netapp you can show locked inodes and it lists them by host. I have no idea about other implementations. I suspect this is very platform dependant. Matt. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
