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
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
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
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
: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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
rsockd
RSOCKD(8) System Manager's Manual RSOCKD(8)
NAME
rsockd - SOCKSified SOCKS server
SYNOPSIS
rsockd [ -ver | -i | -I ]
DESCRIPTION
rsockd is the SOCKSified version of the SOCKS server sockd. Functionally rsockd is identical to sockd except that it may (though not nec-
essarily has to) make use of other SOCKS servers to reach some destinations. A number of rsockd's can be strung together or organized in a
cascade or other more complicated structures to serve the needs of a particular network configuration and restrictions. Obviously this
complicates the issues and make the setup and maintenance of the firewall more difficult. So use sockd instead whenever you can.
This document only describes the features of rsockd that are different from sockd. You should read sockd(5) carefully to gain a basic
understanding of of how the SOCKS server works.
When rsockd receives a request, it checks the request again its configuration (in exactly the same way that sockd does) to decider whether
the request is to be accepted. The primary difference between sockd and rsockd is in how they establish connection to the destination host
of a accepted request. sockd assumes that it can connect directly to the destination host and proceeds to do so. rsockd makes no such
assumption. Instead, it consults another configuration file to decide whether it can connect directly to the particular destination host or
whether it has to use a proxy connection through another SOCKS server. In other words, it behaves just like a versatile SOCKS client in
this regard. Therefore rsockd requires not only the SOCKS server configuration file /etc/sockd.fc or /etc/sockd.conf to decide whether to
accept or reject a request, but also the client configuration file /etc/socks.fc or /etc/socks.conf to decide how to reach the destination
host. If it is a multi-homed version and supports RBIND, it also needs the route file /etc/sockd.fr or /etc/sockd.fr to decide which net-
work interface to use for a connection.
Look at it in a different way, you can think of sockd as a special case of rsockd, one which can connect directly to all destination hosts.
In fact, an rsockd using the client configuration consisting of only this line
direct ALL 0.0.0.0
is functinally identical to the regular sockd.
Anther thing to mention is related to the use of identd. Only the SOCKS server which the requesting host directly connects to can find out
the identity of the real user. Suppose user x on host C connects to rsockd on server B which in turn connects to sockd on server A in order
to reach destination z. Host B can query identd on host C to find out whether the user is indeed x. To host A, the request appears to orig-
inate from user x on host B. An identd query from Host A to host B returns the userid that owns the rsockd process on host B, not the real
user x.
OPTIONS
See sockd(8).
EXAMPLES
The follwoing is an example of the client configuration file. See related man pages for examples on server configuration and route files.
# /etc/socks.conf for rsockd of domain rnd.xyz.com
#
# Use proxy connection through SOCKS server on socks.market.xyz.com
# to reach hosts within market.xyz.com
sockd @=socks.market.xyz.com .market.xyz.com 0.0.0.0
#
# Use direct connect to all other hosts within xyz.com
direct .xyz.com 0.0.0.0
#
# Use proxy connection through SOCKS server on gateway.xyz.com
# to reach all others
sockd @=gateway.xyz.com ALL 0.0.0.0
FILES
/etc/sockd.fc, /etc/sockd.conf, /etc/sockd.fr, /etc/sockd.route, /etc/socks.fc, /etc/socks.conf, /etc/inetd.conf, /etc/services,
/var/adm/messages, /etc/syslog.conf
SEE ALSO
sockd(8), socks_clients(1), sockd.conf(5), sockd.route(5), socks.conf(5), make_sockdfc(8), make_sockdfr(8), dump_sockdfc(8),
dump_sockdfr(8)
AUTHOR
Ying-Da Lee, ylee@syl.dl.nec.com
May 6, 1996 RSOCKD(8)