upgrade lenny, nfs-kernel-server + amd home mounts fail?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Debian nfs-kernel-server and am-utils packages provide NFS automount
services using /net and /home maps. Both maps work on an "early lenny"
server, but something is wrong with home on a bang-up-to-date
"late lenny" server. Gory details follow:
Here is what happens when an NFS client lists an ordinary user
file on the working server:
client# ls /net/earlylenny/export/home1/user1/file.txt
/net/earlylenny/export/home1/user1/file.txt
client# ls /home/user1/file.txt
/home/user1/file.txt
Now for user files on an up-to-date lenny box:
client# ls /net/latelenny/export/home1/user2/file.txt
/net/latelenny/export/home1/user2/file.txt
client# ls /home/user2/file.txt
ls: /home/user2/file.txt: Input/output error
client#
tcpdump sees "Stale NFS file handle" coming from server
user2 was OK on earlylenny, I had to move him. Why don't
I use etch? After about 3 months steady labour its
nfs-kernel-server would start randomly saying
"permission denied". That seems fixed in lenny.
The amd home map is generated by a script from an am-utils
package. It looks like this:
user2 \
host==latelenny;type:=link;fs:=/export/home1/user2 \
rhost:=latelenny;rfs:=/export/home1/user2
net map is Debian default.
Other version info from dpkg and uname:
latelenny:
nfs-kernel-server 1:1.1.2-6lenny1
Linux latelenny 2.6.26-1-686 #1 SMP Wed Nov 26 19:14:11 UTC 2008 i686
GNU/Linux
earlylenny:
nfs-kernel-server 1:1.1.2-6
Linux earlylenny 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686
GNU/Linux
both early and late lennies:
am-utils 6.1.5-12
nfs-common 1:1.1.2-6
I installed the early nfs-kernel-server on latelenny, but it did not fix
the problem. I also tried 1:1.1.2-2 without success.
Has anyone else seen this? I'm not sure of the best way to proceed.
- - Dan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklLW4IACgkQCW+xT8gphKEdMgCgyx4A6sOYeGUY99gXfqWmkvDX
erkAnRp6FsXNrqwioarI0z8d6kD0rcgr
=nENP
-----END PGP SIGNATURE-----
Reply to: