Re: NFS Problem in Kernel 2.0.27: inode status not updated

> You are right. That is a big issue. Perhaps simply locking by creation
> of the mbox.open file and checking the error code is more reliable?

... than hitching posts ? Pass ...

> I know that many people have already spent their time on figuring out a
> reliable way to lock across NFS but maybe there is no way.

Ditch it, and use lockd ...

> We could try to make linux NFS creat() call atomic (Perhaps it already is
> given the need for reliable locks?) resulting in a reliable locking with
> simply creating the lock file.

Not the way to go ...

> Linux NFS is currently in the revision process

Forget it -- not the way to go.

> and there is an experimental lockd available (does not work though ...)

Yes -- lockd is the way to go.
All systems should have it.
Linux's version has been very slow a comin', and as you say, it's not yet there
.....