After we have been burnt, we became pretty quick to diagnose as NFS
errors problems that were to be found elsewhere.
Here are a few, which you may check before reporting similar cases:
Transcript:
% ct setcs foo cleartool: Error: Operation stat, ./..: Stale NFS file handle cleartool: Warning: New config spec makes current working dir invisible.
The problem was with the config spec itself, which didn't select any version of the parent directory (as clearly stated in the error message).
As part of a normal build, the exact same message we had, but with a plain error instead of a warning and a retry:
Now looking at library libtgeti.a clearmake: Error: Error opening CR cache file .cmake.state - Permission denied "lib" is up to date.
The problem was however only a spelling error in the macro naming the directory to the library: the result was that one tried to build with clearmake in the root directory '/', and there was a real permission denial in creating a .cmake.state file there.