> Mount another Linux system (ocs3, 2.0.35) on NFS. Disconnect ocs3 from
> the LAN. All attempts to getcwd() take ages with timeout messages :-
>
> nfs: server ocs3 not responding, timed out
> nfs_revalidate_inode: /// getattr failed, ino=1476395010, error=-5
> shell-init: could not get current directory: getwd: cannot access parent directories
> nfs: server ocs3 not responding, timed out
> nfs_revalidate_inode: /// getattr failed, ino=1476395010, error=-5
> job-working-directory: could not get current directory: getwd: cannot access parent directories
>
> getcwd() runs up the directory tree, if its search algorithm crosses
> the disconnected NFS mount point it tries to access the remote system.
> Not good when a remote system drops off, even users who are not using
> ocs3 directories are hit. Lots of tasks invoke getcwd().
Hi Keith,
I can see that this would be massively annoying, and in this case the
attempts at revalidation don't make a lot of sense, as there's not much
the client can do if something gets scrambled on the server.
I'll ponder it a while and try to come up with a solution ...
Regards,
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html