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

From: Thomas Petersen
Date: Mon Jun 22 2009 - 16:02:35 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sven Geggus wrote:

> Trond Myklebust <trond.myklebust@xxxxxxxxxx> 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--
> /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)


I switched to 2.6.29 on my server yesterday. It seemed to work fine but
a few hours ago I began to get the same errors (reconnect_path: npd != pd).
I have a diskless client which received stale nfs handles and stopped
working properly. I have a laptop also which is still working ok but
that client doesn't utilize the nfs filesystems that much.

I'm using gentoo on all computers. Both clients are using 2.6.28. Server
switched from 2.6.27 to 2.6.29.
I am using XFS on the server !

There is a special thing about the server though and until I saw this
discussion I thought that was the problem:
I updated the kernel because I also replaced the hardware (except the
harddrives). I switched from an old AMD Athlon (32 bit) to an AMD Phenom
II (64 bit, 4 cores). The new kernel is compiled in 64 bit but all
userland is still the old 32 bit compiled on the old Athlon. Everything
runs through IA32 emulation.

Both clients are 32 bit machines.

In a few days I'll start to update to 64 bit userland on the server and
see if that has an effect on the problem.


Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko/4boACgkQOaC6N60T7rze2gCfVRHI6H5hzyC4eX80H2hywJ81
3/QAnA17/9MEO3Zm8eosOtfzU+q3sYi6
=fgT+
-----END PGP SIGNATURE-----
--
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/