...because only clients that are currently holding POSIX locks will have an
entry.
> - Why do most entries' mtime get updated periodically, but a few of
> the entries go stale with time?
The file should get deleted every time the client releases all locks and
successfully manages to notify the server that it is stopping monitoring.
> - Why do some of the stale entries get left over even after the
> workstations have halted (these ones present the nfs hang issue)?
As I've told you before: 'stale' entries, as you call them, indicate that the
rpc.statd never managed to notify the server that it should stop monitoring.
It indicates either the server or the client crashed before the POSIX locks
held by the client got released, or possibly that the rpc.statd processes
crashed (or got 'kill -9' ed).
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/