Sponsored Content
Operating Systems Solaris NFS write error on host xyz: Stale NFS file handle - Solaris 10 Post 303005256 by jim mcnamara on Monday 16th of October 2017 09:57:46 AM
Old 10-16-2017
NFS has an inherent problem. It is not very good at knowing if the mounted resource is available or not, so it depends on a response from the host providing the resource - but only after some applications asks for it.

Example NFS4 on a Solaris 10 machine used to hang shutdown when a user executed a cd to the NFS directory, and then just left the process sitting. The machine had zones (virtuals) and some NFS connections were required from zone to zone. Not a great idea.

This meant that if NFS zone1 -> zone2 and zone2 was taken down, the machine would not reboot because NFS could not figure out how close the open file, and NFS will wait for long periods of time for a resource.

You may have what amounts to a similar problem. A user on one machine has an NFS mounted directory open - the directory lives on another virtual or machine. Something happens on the remote and the local one hangs. NFS has problems, avoid it if you can. NFS can negatively affect simple commands like pwd and system calls like realpath() if the parent directory of your current directory has an external NFS mount. And that directory no long is available.
This User Gave Thanks to jim mcnamara For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NFS file handle

How can I kill mount connection(NFS , made by automount) if remote filesystem is down? I tried: fuser -ku /auto /auto: umount /auto nfs umount: ERROR: /auto is busy If I try cd /auto - I get - /auto: Stale remote file handle. I know that reboot will help but I cannot reboot this... (2 Replies)
Discussion started by: kazimir
2 Replies

2. UNIX for Advanced & Expert Users

Stale NFS file handle

Hi, I get an error saying "Stale NFS file handle" how can I solve this? Is it possible to do this with a umount/ mount command? (5 Replies)
Discussion started by: rein
5 Replies

3. Solaris

Error Message: find: cannot open /: Stale NFS file handle

I am using the "find" command below and it respond with the error message " find: cannot open /: Stale NFS file handle" what does it mean? what can I do about it? Need advice, thanks. below are the command that I enter, the respond and the error message: root@ScripServer:/# find / -name... (1 Reply)
Discussion started by: ezsurf
1 Replies

4. Solaris

NFS write error on host : Stale NFS file handle

:confused:Hi all When i see in the /var/adm/messages, i saw the following error unix: NFS write error on host : Stale NFS file handle. unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49) It is using sunOS 5.7. Is anybody know what is this error? Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies

5. UNIX and Linux Applications

Stale NFS file handle

There are a filesystem /GWD/appbase/projects/GRIDDB Under this filesystem there is a directory called backup. But When I am trying to access the backup directory ,it is showing me the following error: # cd /GWD/appbase/projects/GRIDDB # cd backup -bash: cd: backup: Stale NFS file handle ... (3 Replies)
Discussion started by: alphasahoo
3 Replies

6. Linux

NFS file handle question

Hello All, I have a small question regarding the NFS file handles. Suppose I have a NFS client who has requested for a particular file from the NFS server.Now lets assume that I am using a NFS v2 server. So I get the filehandle for that file and I can use it. Suppose later I upgrade the server to... (0 Replies)
Discussion started by: prathamesh
0 Replies

7. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

8. UNIX for Advanced & Expert Users

How to decode nfs file handle in HP-UX?

Hi Experts, Any idea how to decode file handle in HP-UX? I am getting the following error continously in my HP-UX 11.31 box :mad: Apr 26 07:15:00 host62 su: + tty?? root-bb Apr 26 07:15:00 host62 su: + tty?? root-abcadm Apr 26 07:15:01 host62 vmunix: NFS write error on host peq9vs:... (1 Reply)
Discussion started by: vipinable
1 Replies

9. UNIX for Advanced & Expert Users

What is a file handle? for NFS troubleshooting stale issue.

Experts, Can any one please explain about a "File Handle" , what it is. Can we see it, like an inode number. - Also what is the significance of it in "Stale NFS file handle" error. Thanks, (3 Replies)
Discussion started by: rveri
3 Replies

10. AIX

NFS multiple write error.

Hi, We are taking the mksysb backup to NIM server's NFS mount point (/backup). We have mounted /backup to all the clients /backup and full permission. When multiple mksysb backup starting simultaneously to the NIM server's shared NFS mount point then only one backup is running and all others... (3 Replies)
Discussion started by: sunnybee
3 Replies
RPC.UMNTALL(8)						    BSD System Manager's Manual 					    RPC.UMNTALL(8)

NAME
rpc.umntall -- notify NFS servers about unmounted NFS file systems SYNOPSIS
rpc.umntall [-e expire] [-h host] [-k] [-p remotepath] [-v] DESCRIPTION
The rpc.umntall utility is proposed in the NFS RPC specification; see NFS Version 3 Protocol Specification, RFC 1813, Appendix I. It uses remote procedure calls to remove mount entries from /var/db/mountdtab on the remote NFS server. It is called automatically without any parameters during startup and shutdown of the system. This ensures that showmount(8) does not display old and expired entries. The rpc.umntall utility is only needed on client side, where mount_nfs(8) adds a mount entry with the current date to /var/db/mounttab, and umount(8) removes the entry again. The rpc.umntall utility cares about all remaining entries in this table which result from crashes or unproper shutdowns. The options are as follows: -e expire All entries which are not actually mounted or older than expire (seconds) are removed from /var/db/mounttab. This may be the case for DNS changes or long out of service periods. Default expire time is 86400 seconds (one day). -h host Only remove the specific hostname. Send a UMNTALL RPC to the NFS server. -k Keep entries for existing NFS file systems. Compare the NFS file systems from the mounttab against the kernel mountlist and do not send the RPC to existing mount entries. Useful during startup of the system. It may be possible that there are already mounted NFS file systems, so calling RPC UMOUNT is not a good idea. This is the case if the user has rebooted to 'single user mode' and starts up the system again. -p path Only remove the specific mount-path. Send a UMOUNT RPC to the NFS server. This option implies the -host option. -v Verbose, additional information is printed for each processed mounttab entry. FILES
/var/db/mounttab mounted nfs-file systems SEE ALSO
mount_nfs(8), mountd(8), umount(8) HISTORY
The rpc.umntall utility first appeared in FreeBSD 4.0. AUTHORS
Martin Blapp <mb@imp.ch> BSD
November 17, 1999 BSD
All times are GMT -4. The time now is 04:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy