Sponsored Content
Operating Systems Solaris NFS write error on host xyz: Stale NFS file handle - Solaris 10 Post 303005253 by psychocandy on Monday 16th of October 2017 09:16:17 AM
Old 10-16-2017
Sorry forgot to say the host is actually a storage array. i.e. xyz

Also, there are lots of mount points on this particular client. I'll try them all...


Would you expect this error to re-occur? Would be useful for future reference if there was a way to decrypt the file handle too (Although I guess not so easy if the host is not solaris).
 

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
on(1)							      General Commands Manual							     on(1)

NAME
on - execute command on remote host with environment similar to local SYNOPSIS
| host [command [argument] ... ] DESCRIPTION
executes a command on a remote host, using an environment similar to that of the invoking user where: host specifies the name of the host on which to execute the command. command specifies the command to execute on host If command is not specified, starts a shell on host. argument ... is a list of arguments for command. The user's environment variables are copied to the remote host, and the file system containing the user's current working directory is NFS mounted on the remote host (see nfs(7)). The command is executed on the remote host in the user's current working directory. Commands using relative path names that reference file system objects within the user's current working file system have the same behavior as running the command on the client. The behavior of commands using relative path names that cross the file system boundary or commands using absolute path names depends on the organization of the remote host's file system. Implicit and explicit use of environment variables may also cause a command's behavior to be dependent on the organization of the remote host's file system. For example, the environment variable usually contains absolute path names. Standard input, output and error of the remote command are connected to the appropriate file descriptors on the client. The remote execution daemon does not allow to execute a remote command. The signals and are propagated to the remote command. and are ignored by the remote command. All other signals are delivered to the com- mand. In order to execute a remote command, the remote host must be configured to execute (see rexd(1M)). Options recognizes the following options: Interactive mode. This option is required for commands that must communicate with a terminal such as or Terminal mode changes are propagated to the server. The standard input for an interactive command must be a tty device. The and options are mutually exclusive. Debug mode. Print diagnostic messages during startup of the command. These messages are useful for detecting configuration problems if the command to a specific host is failing. No input mode. This option causes the remote command to get end-of-file (EOF) when it reads from standard input, instead of connecting the standard input of the command to the standard input of the remote command. The option is required when running commands in the background. The and options are mutually exclusive. DIAGNOSTICS
The host name host was not found in the hosts database. The host host is down, unreachable on the network, or not running A problem occurred trying to find the user's current working directory (current_dir). A problem occurred trying to determine the mount point of the user's current working directory (current_dir). The standard input (stdin) of the command with the option is not a tty device. Errors that occur on the server server are propagated back to the client. These messages are documented in the DIAGNOSTICS section of rexd(1M). AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
exports(4), rexd(1M). on(1)
All times are GMT -4. The time now is 05:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy