Sponsored Content
Full Discussion: Stale NFS file handle
Top Forums UNIX for Advanced & Expert Users Stale NFS file handle Post 61159 by rein on Sunday 30th of January 2005 11:05:26 AM
Old 01-30-2005
/xanext1/home on l102f1.stor.appshost.net:/vol/snapshot/xanext1_admin/home rsize=16384,wsize=16384,NFSv3,dev=60000029 on Wed Jan 19 17:08:23 2005

it was mounted read & write

data is still there
 

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. Programming

deleting a file name by its handle

All, I am having three function 1.open 2.process 3.close. Open will open a file and process will process a file and close will close the file .. I can able to close the file by its filehandler.Is there is anyway that i can get the file name by filehandle and remove it after... (5 Replies)
Discussion started by: arunkumar_mca
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

Before I delete any file in Unix, How can I check no open file handle is pointing to that file?

I know how to check if any file has a unix process using a file by looking at 'lsof <fullpath/filename>' command. I think using lsof is very expensive. Also to make it accurate we need to inlcude fullpath of the file. Is there another command that can tell if a file has a truely active... (12 Replies)
Discussion started by: kchinnam
12 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. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400) Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies
mount(8nfs)															       mount(8nfs)

Name
       mount, umount - mount and unmount a Network File System (NFS)

Syntax
       /etc/mount [ -t nfs -f -r -v ] [ options ] device directory

       /etc/umount [ -v ] directory

Description
       The  command  allows  you  to  mount  a file system or directory onto a directory.  Once a file system or directory has been mounted, it is
       treated as a file system.

       The argument device can have one of the following forms:

	      host:remote_name

	      remote_name@host

       The remote_name is the name of a file system or subtree of a file system that has been exported by host.  The file directory must exist and
       must be a directory.  It becomes the name of the newly mounted file system.

       General users can mount file systems with certain restrictions in addition to those listed in

       The command unmounts the remote file system that was previously mounted on the specified directory.

Options
       See the reference page for a description of the -t option.

       -f	   Fast  unmount.   The  -f  option  has no meaning for local file systems and directories.  However, for remote file system types
		   (such as NFS), the -f option causes the client to unmount the remotely mounted file systems and directories	without  notifying
		   the server.	This can avoid the delay of waiting for acknowledgment from a server that is down.

       -r	   Indicates that the file system is to be mounted read only.

       -v	   Tells what did or did not happen.  (Verbose flag)

       -o options  Specifies options as a sequence of words, separated by commas, from the list that follows.  The default options are as follows:
		   rw,hard,intr,retry=10,000,timeo=11,retrans=4, 
		   port=NFS_PORT,pgthresh=64
		   Defaults for rsize and wsize are set by the kernel.	The NFS options are as follows:

		   bg		 If the first mount attempt fails, retry the mount in the background the number of times specified (the default is
				 10,000 times).

		   hard 	 Retry the NFS operation (not the mount) request until server responds.  The hard option  applies  after  the  has
				 succeeded.  Use the hard option when mounting (read-write) file systems.

		   intr 	 Allow hard mounted file system operations to be interrupted.

		   nintr	 Disallow hard mounted file system operations from being interrupted.

		   noexec	 Binaries cannot be executed from this file system.

		   nosuid	 The and programs can not be executed from this file system.

		   pgthresh=##	 Set the paging threshold for this file system in kilobytes.

		   port=n	 Set server IP port number to n.

		   retrans=n	 Set number of NFS operation retransmissions (not the mount) to n.  The retrans= option applies after the has suc-
				 ceeded.

		   retry=n	 Set number of mount failure retries to n.  The retry= option applies to the command, itself.

		   ro		 Read-only.

		   rsize=n	 Set read buffer size to n bytes.

		   rw		 Read/write.

		   soft 	 Return an error if the server does not respond to the NFS operation (not the mount)  request.	 The  soft  option
				 applies after the has succeeded.  Do not use the soft option to mount (read-write) file systems.

		   timeo=n	 Set NFS timeout to n tenths of a second.

		   wsize=n	 Set write buffer size to n bytes.

		   The	following  options  affect  how  quickly  you  see  updates to a file or directory that has been modified by another host.
		   Increasing these values will give you slightly better performance.  Decreasing these values decreases the time it takes for you
		   to  see  modifications  made  on  another host.  If you are the only modifier of files under this mount point, you can increase
		   these values.

		   acdirmin=n	 Hold cached directory attributes for at least n seconds.  The default is 30 seconds.

		   acdirmax=n	 Hold cached directory attributes for no more than n seconds.  The default  is	60  seconds.   The  maximum  value
				 allowed is 3600.

		   acregmin=n	 Hold cached file attributes for at least n seconds.  The default is 3 seconds.

		   acregmax=n	 Hold cached file attributes for no more than n seconds.  The default is 60 seconds.  The maximum value allowed is
				 3600.

		   actimeo=n	 Set all four attributes cache timeout values to n.

		   noac 	 Do not set attribute caching.	This is equivalent to actimeo=0.

       The option causes to run in the background if the server's daemon does not respond.  The command attempts each request retry=n times before
       giving  up.   Once  the file system is mounted, each NFS request made in the kernel waits timeo=n tenths of a second for a response.  If no
       response arrives, the time-out is multiplied by 2 and the request is retransmitted.

       When retrans=n retransmissions have been sent with no reply, a soft mounted file system returns an error on the request and a hard  mounted
       file  system  retries the request.  If a hard mounted file system was mounted with the option, an operation within that file system that is
       retrying (for example, the server is down) can be interrupted.  File systems that are mounted (read-write) should use the hard option.  The
       number  of bytes in a read or write request can be set with the and options. The values for and must be between 512 and 8192, and be a mul-
       tiple of 512.

       The option for is:

       -v     Tells what did or did not happen.  (Verbose flag)

Restrictions
       If the directory on which a file system is to be mounted is a symbolic link, the file system is mounted on the directory to which the  sym-
       bolic link refers, rather than being mounted on top of the symbolic link itself.

       The and commands should only be invoked by the and commands.  It is recommended that users (and superusers) do not invoke the and commands.
       An exception to this rule is the use of the -b command in the file. The -b command broadcasts a message informing  NFS  servers	that  this
       machine	no  longer has any NFS filesystems mounted. This is done in case the machine had crashed while it had NFS filesystems mounted. The
       servers use this information to clean up their tables. The command automatically adds the -b line to the file on NFS client systems.

Examples
       The command invokes to do its work.  A sample command is:

	    # mount -t nfs -o hard,pgthresh=100 server:/usr /usr

       To mount the remote file system onto the local directory with 1k transfer size, type:

	    # mount -t nfs -o rsize=1024,wsize=1024 serv:/usr/src /mnt

       To mount the remote directory onto the local directory type:

	    # mount -t nfs serv:/usr/src/code /usr/src

       To hard mount a remote file system called onto the local directory type:

	    # mount -t nfs -o hard serv:/usr/src /usr/src

Files
       File system information file

       NFS-specific mount program

       NFS-specific unmount program

See Also
       getmnt(2), mount(2), fstab(5), exports(5nfs), mount(8), umount(8), mountd(8nfs), rmtab(5nfs), nfssetup(8nfs)

																       mount(8nfs)
All times are GMT -4. The time now is 12:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy