OK, sorry for the spam, I forgot to modprobe rpcsec_gss_krb5 kernel
module on the client.
All the described problems were harmless.
The incorrect warning about rpc.gssd not running was fixed in Edgy, but it
doesn't cause any problems.
--
add NFSv4 support
https://launchpad.net/bugs/27425
--
u
OK, I had an old version of mount because of the package loop-aes-utils
that I've installed some time ago to mount an old filesystem encrypted
with loop-AES and migrate it to LUKS.
Now I've removed that package and restored the original mount.
It shows the following version:
# mount -V
mount: mo
Regarding the search for mount.nfs4 - mount does this, but it appears
earlier in the strace, so it's not visible above.
Here's the relevant strace fragment:
lstat64("/etc/mtab", {st_mode=S_IFREG|0644, st_size=484, ...}) = 0
stat64("/sbin/mount.nfs4", 0xbf81582c) = -1 ENOENT (No such file o
The most suspicious behaviour of mount is the double attempt at closing
the TCP socket it has opened to the NFS server. Notice this fragment in
the strace:
---
connect(3, {sa_family=AF_INET, sin_port=htons(2049),
sin_addr=inet_addr("192.168.1.1")}, 16) = 0
gettimeofday({1173993083, 563383}, NULL)
Mount looks for /var/run/rpc.gssd, while the real pidfile is
/var/run/rpc.gssd.pid on Dapper.
--
add NFSv4 support
https://launchpad.net/bugs/27425
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
That's strange, I have the very same versions, yet mount still tries to
find mount.nfs4 and fails:
[EMAIL PROTECTED]:~$ dpkg -l nfs-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-
Oh, and the error I get from mount isn't very helpful:
-
mount: wrong fs type, bad option, bad superblock on stacja.amarczuk:/home/nfs/,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
-
No