Re: 2.6.29+ NFS-Server Problem "reconnect_path: npd != pd"

[Trond Myklebust <trond.myklebust@fys.uio.no>]

On Thu, 2009-05-21 at 17:48 +0000, Sven Geggus wrote:
> Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> 
> > So what is the underlying filesystem that you are exporting, and what
> > does your /etc/exports file look like?
> 
> The underlying filesystem is xfs and /etc/exports (unchanged) is here:
> 
> --cut--
> # /etc/exports: the access control list for filesystems which may be exported
> #		to NFS clients.  See exports(5).
> /               192.168.3.2(rw,no_root_squash,async,subtree_check)
> /home/sven	192.168.3.2(rw,no_root_squash,async,subtree_check) 192.168.3.6(rw,no_root_squash,async,subtree_check) 192.168.3.8(rw,no_root_squash,async,subtree_check)
> /home/mp3	192.168.3.2(rw,no_root_squash,async,subtree_check) 192.168.3.6(rw,no_root_squash,async,subtree_check) 192.168.3.8(rw,no_root_squash,async,subtree_check)
> /home/sven/filme 192.168.3.7(ro,async,subtree_check)
> /home/kathi910	192.168.3.7(rw,no_root_squash,async,no_subtree_check)
> --cut--
> 
> 192.168.3.2 is the client which causes the error, I didn't notice the
> error on the other clients, but they are not used that often.
> 
> Especially 192.168.3.7 does seem to work.
> 
> Regards
> 
> Sven
> 

Reforwarding the reply for the benefit of the NFS mailing list. Not
everyone reads lkml...

Trond