[Sunhelp] [Help] Stale NFS filehandles

[Rick Lantaigne]

- NFS file handles encode the server's filesystem ID and the file's inode number
and the inode's generation to uniquely identify each NFS-mounted file.

- Any actions that you do that will change the inode # at the server end will end
up creating a stale NFS mount for those clients that were mounted.  the only way
to clear the clients are to get them in a position that the stale mount can be
unmounted.

- Tools to use:
fuser  : identify process and user  using the stale mount
df : identify the stale  mount
mount: get the actual

read : http://www.Sun.COM:80/sunworldonline/swol-10-1995/swol-10-sysadmin.html



Sorry  no time to go into more details.  Read the stuff at the above URL for how
to information.


Rick

- - - - - - - - - - - - - - - - - - -
Robert.Cross at scottish-newcastle.co.uk wrote:

> We've just moved one of our NFS servers from a Solaris 2.4 system to a Solaris
> 2.6 one. After the
> change we seem to get a lot more 'stale NFS file handle' messages on our
> (Solaris) clients. Is there
> some timeout value that I can change to increase the time before which the NFS
> link goes stale?
>
> Thanks
>
> Robert Cross, Systems Programmer, Scottish & Newcastle plc
> (Apologies for the legal jargon that follows....)
>
> **********************************************************************
> The information contained in this message and any attachments:
>
> 1. does not constitute an offer or an acceptance of an offer or a
> representation or warranty, nor shall it form any part of a legally
> binding contract.
>
> 2. has been compiled with care but no representation or warranty
> (express or implied) is made as to its accuracy or completeness and no
> liability can be accepted for any loss arising from the use of any of
> the information.
>
> 3. may include opinions or views, which unless expressly stated
> otherwise, are not those of the company or any person in relation to
> whom the company would have vicarious liability or responsibility.
>
> 4. is not guaranteed to be free from any so-called computer viruses
> and it is strongly recommended that you check for such viruses before
> down-loading it to your computer equipment.
>
> 5. may include hypertext links to the sites of other companies or
> persons, the content of which this company has no control over and
> accepts no liability for.
>
> 6. is for the exclusive use of the addressee and may contain confidential,
> privileged, work product immunity and/or non-disclosable information.
> If you are not the intended recipient and receive this message and any
> attachments, you must not read, copy, transmit, disclose or otherwise use
> any of them (or part of them) in any way (to do so may be unlawful) and
> we would be grateful if you could inform us immediately of any such
> receipt and subsequently entirely and permanently erase the message and
> any attachments from your equipment.
>
> E-mail is an informal method of communication and is subject to
> possible data corruption.  For these reasons it will normally be
> inappropriate to rely upon information contained in an e-mail without
> obtaining tangible written confirmation of it.
> **********************************************************************

--

--- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ---
Rick Lantaigne                              CSA Supervisor

Nortel Networks
185 Corkstown Road,             Voice :     (613) 763-4677
Dept: 5U14, M.S.: 047,            Fax :     (613) 763-8825
Nepean, ON, Canada                ESN :           393-4677
K2H 8V4                 Inet : lantaign at nortelnetworks.com
--- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- ---