Messages in this thread | | | From | Keith Owens <> | Subject | NFS mounts confuse getcwd() | Date | Sun, 13 Sep 1998 20:29:02 +1000 |
| |
2.1.121, mount 2.7l. No knfsd, just rpc.mountd and rpc.nfsd.
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().
- 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
| |