From: Thomas Petersen <thomas@mendo.dk>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.29+ NFS-Server Problem "reconnect_path: npd != pd"
Date: Mon, 22 Jun 2009 21:55:38 +0200 [thread overview]
Message-ID: <4A3FE1BA.10908@mendo.dk> (raw)
In-Reply-To: <gv4463$6fn$1@ultimate100.geggus.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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--
> /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-----
prev parent reply other threads:[~2009-06-22 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 14:20 2.6.29+ NFS-Server Problem "reconnect_path: npd != pd" Sven Geggus
2009-05-21 16:49 ` Trond Myklebust
2009-05-21 16:57 ` Sven Geggus
2009-05-21 17:32 ` Trond Myklebust
2009-05-21 17:48 ` Sven Geggus
2009-05-21 18:12 ` Trond Myklebust
2009-05-28 20:28 ` J. Bruce Fields
2009-05-28 20:32 ` Sven Geggus
2009-06-19 12:14 ` Mathias Kretschmer
2009-06-19 12:46 ` Sven Geggus
2009-06-27 19:39 ` Leandro Lucarella
2009-06-22 19:55 ` Thomas Petersen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A3FE1BA.10908@mendo.dk \
--to=thomas@mendo.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox