Actually fuser -k <filesystem> will kill ALL processes associated with the
filesystem, processes that have files open for input or output on it and
processes with a current working directory on it.  This is not really a good
idea.  Killing processes such as init, syncer, et al can have a somewhat
deleterious affect on system stability.




 (Embedded
 image moved   Jeffrey Fulmer <jfulmer AT WHITEOAKNET DOT COM>
 to file:      05/27/99 06:53 PM
 pic17120.pcx)




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Chuck Mattern/IS/SSC/THD)
Subject:  Re: Stale NFS handle




I solved the problem with "fuser -k <filesystem_name>"  this kills any NFS
process associated with the file system.  I don't know why I am getting this
error on a system that is not running NFS.  But when I ran fuser, it did
report that it was killing a PID.

Jeff

Jim Hicks wrote:

> Jeff,
> Did you get anywhere with the 'stale nfs mount' message?  I also am getting
> this error on "/" filesystem.  The backup will abort and skip this
> filesystem but continues on with other filesystems etc. to completion.
> ADSM client  3.1.20.6   AIX 4.3.1.0 on SP.
>
> I tried Eric's suggestion of NFSTIMEOUT 10  to no avail.  There is no NFS
> mounts on the node I'm using....
>
> Jeffrey Fulmer wrote:
>
> > Thanks,
> >
> > I really should have posted this somewhere else.  This is an AIX problem
> > and not related to ADSM.  I ran "fuser -k" on the filesystem and ADSM
> > backed it up that evening.  But I can't figure out why I am getting a
> > stale handle on a system that is NOT even running NFS.
> >
> > Cheers,
> > Jeff
> >
> > Eric Tang wrote:
> >
> > > You can try adding undocumented parm in dsm.sys    NFSTIMEOUT     10
> > >
> > > Regards,

> > > Eric Tang