NFSv4 will help: it does notice a no longer held lock, in contrast to NFSv3, that will not notice a no longer held lock (and will hold the lock indefinately).
The problem is, that even after removing lock and .parentlock, a couple of .sqlite files will still be locked on an NFSv3 server.
A workaround we used is to copy the whole profile, then rename the new profile to go over the old one; then remove the old profile. The new profile will have no locked files on the server, so it will work.
NFSv4 will help: it does notice a no longer held lock, in contrast to NFSv3, that will not notice a no longer held lock (and will hold the lock indefinately).
The problem is, that even after removing lock and .parentlock, a couple of .sqlite files will still be locked on an NFSv3 server.
A workaround we used is to copy the whole profile, then rename the new profile to go over the old one; then remove the old profile. The new profile will have no locked files on the server, so it will work.