Sponsored Content
Operating Systems Solaris NFS write error on host : Stale NFS file handle Post 302179122 by sparcguy on Thursday 27th of March 2008 03:42:41 AM
Old 03-27-2008
Depends, this stale file hander normally appears when the server whom you are mounting the filesystem resource from is no longer available or something in the network is blocking.

Or

In a cluster during failover of NFS resource the major & minor numbers on the secondary server taking over is different from that of the primary then it's a system configuration problem
 

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

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

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

7. AIX

Write once on NFS file system

Hello Guru's We are trying to save some data for 10 -15 yrs. so we created a NFS share file system and mounted on AIX 5.3 servers, keeping in mind that we might need to replace the expired disk/bad disk every 2 yrs or 4 yrs. Now we are trying to solve. How to protect it from getting deleted... (6 Replies)
Discussion started by: Beginner123
6 Replies

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

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

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
OCF_HEARTBEAT_EXPORT(7) 					OCF resource agents					   OCF_HEARTBEAT_EXPORT(7)

NAME
ocf_heartbeat_exportfs - Manages NFS exports SYNOPSIS
exportfs [start | stop | monitor | meta-data | validate-all] DESCRIPTION
Exportfs uses the exportfs command to add/remove nfs exports. It does NOT manage the nfs server daemon. It depends on Linux specific NFS implementation details, so is considered not portable to other platforms yet. SUPPORTED PARAMETERS
clientspec The client specification allowing remote machines to mount the directory over NFS. (required, string, no default) options The options to pass to exportfs for the exported directory. (optional, string, no default) directory The directory which you wish to export using NFS. (required, string, no default) fsid The fsid option to pass to exportfs. This can be a unique positive integer, a UUID, or the special string "root" which is functionally identical to numeric fsid of 0. 0 (root) identifies the export as the root of an NFSv4 pseudofilesystem -- avoid this setting unless you understand its special status. This value will override any fsid provided via the options parameter. (unique, required, string, no default) unlock_on_stop Relinquish NFS locks associated with this filesystem when the resource stops. Enabling this parameter is highly recommended unless the path exported by this exportfs resource is also exported by a different resource. (optional, boolean, default 0) wait_for_leasetime_on_stop When stopping (unexporting), wait out the NFSv4 lease time. Only after all leases have expired does the NFS kernel server relinquish all server-side handles on the exported filesystem. If this exportfs resource manages an export that resides on a mount point designed to fail over along with the NFS export itself, then enabling this parameter will ensure such failover is working properly. Note that when this parameter is set, your stop timeout MUST accommodate for the wait period. This parameter is safe to disable if none of your NFS clients are using NFS version 4 or later. (optional, boolean, default 0) rmtab_backup Back up those entries from the NFS rmtab that apply to the exported directory, to the specified backup file. The filename is interpreted as relative to the exported directory. This backup is required if clients are connecting to the export via NFSv3 over TCP. Note that a configured monitor operation is required for this functionality. To disable rmtab backups, set this parameter to the special string "none". (optional, string, default ".rmtab") SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 40. stop Stops the resource. Suggested minimum timeout: 10. monitor Performs a detailed status check. Suggested minimum timeout: 20. Suggested interval: 10. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 30. EXAMPLE
The following is an example configuration for a exportfs resource using the crm(8) shell: primitive p_exportfs ocf:heartbeat:exportfs params clientspec=string directory=string fsid=string op monitor depth="0" timeout="20" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/exportfs_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_EXPORT(7)
All times are GMT -4. The time now is 08:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy