Re: nfs stale filehandle issues with 2.6.10-rc1 in-kernel server

[Jeff Garzik]

Trond Myklebust wrote:
> ty den 02.11.2004 Klokka 16:02 (+0400) skreiv Brad Campbell:
>
>
> > /raid 192.168.2.81(rw,async,no_root_squash)
> > /raid 192.168.3.80(rw,async,no_root_squash)
> > /raid0 192.168.2.81(rw,async,no_root_squash)
> > /raid0/tmp 192.168.2.81(rw,async,no_root_squash)
> > /raid2 192.168.2.81(rw,async,no_root_squash)
> > /raid2 192.168.3.80(rw,async,no_root_squash)
> > /nfsroot 192.168.2.81(rw,async,no_root_squash)
>
>
> You should only have 1 line per directory.
>
> You are not allowed to export a directory and its child (unless the
> child is on a different partition - which does not appear to be the case
> here).
>
>   http://nfs.sourceforge.net/nfs-howto/server.html#CONFIG


I'm also seeing stale filehandle problems here in recent kernels.

Setup:  x86 or x86-64, TCP, NFSv4 compiled in to both server and client, 
but not specified in mount options.

This is readily reproducible with rsync -- I just boot to an earlier 
version of the kernel on the NFS client, and the stale filehandle 
problems go away.

	JEff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/