[lkml]   [2001]   [Feb]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Stale NFS handles on 2.4.2
On Saturday February 24, wrote:
[problem summary: After restarting knfsd server on 2.4.2, client
reports Stale NFS file handle]

> On Sun, Feb 25, 2001 at 04:43:46PM +1100, Neil Brown wrote:
> > So check that /etc/exports contains the right info.
> > Check that /var/lib/nfs/rmtab lists the filesystems and clients that
> > you expect to have access, and then run "exportfs -av"
> checked, verified, re-exported, still Stale NFS file handle on client.
> I also used tcpdump on server and when I do ls on my home directory
> (this is where I see the Stale NFS message), it does not generate any
> network traffic. It can't be the server if the client isn't asking
> for it.

Verrry odd. I can see why you were suspecting a cache.
I'm probably going to have to palm this off to Trond, the NFS client
maintainer (are you listening Trond?) but could please confirm that
from the client you can:

1/ ping server
2/ rpcinfo -p server
3/ showmount -e server
4/ mount server:/exported/filesys /some/other/mount/point

If all of these work, them I am mistified. If one of these fails,
then that might point the way to further investigation.


> > > Both server and client are running 2.4.2.
> > >
> > > I'ved tried `mount /home -o remount`, and reading lots of other
> > > directories to flush out that entry if it was in cache without any
> > > results.
> > >
> > > I was hopping to avoid unmounting, as I would have to shut about
> > > everything down to do that.
> --
> +---------------------------------+
> | David Fries |
> | |
> +---------------------------------+
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:17    [W:0.144 / U:1.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site