-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-07-14 at 12:00 +0400, Andrey Borzenkov wrote:
В Sun, 14 Jul 2013 00:22:48 +0200 (CEST) "Carlos E. R." <> пишет:
[...]
Did package reach the server at all? Use tcpdump/tshark to verify.
The server firewall logs the package as being allowed, so yes, it does reach the server.
Did you try to disable firewall on both client and server to be sure it does not influence it?
No... but I will, just in case. [...] No, failure: minas-tirith:~ # SuSEfirewall2 stop SuSEfirewall2: Firewall rules unloaded. minas-tirith:~ # date --rfc-3339=seconds ; time mount -v /var/cache/zypp/nfs_packages/ ; date --rfc-3339=seconds 2013-07-14 15:10:35+02:00 mount.nfs: timeout set for Sun Jul 14 15:12:35 2013 mount.nfs: trying text-based options 'nfsvers=4,addr=192.168.1.14,clientaddr=192.168.1.129' mount.nfs: mount(2): Connection timed out mount.nfs: Connection timed out real 3m0.542s user 0m0.001s sys 0m0.003s 2013-07-14 15:13:35+02:00 minas-tirith:~ # SuSEfirewall2 start SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: Firewall rules successfully set minas-tirith:~ # Notice that the test says that it will time out at 15:12:35, but it does timeout at 15:13:35, ie, one minute more.
It is quite possible that in the past it silently used NFS V3 without you be aware of it.
Maybe. But IIRC, I think that when the server was upgraded to 12.1, I had to specify version 4 for it to work. The previous fstab line on the laptop was this: #192.168.1.14:/data/storage_c/repositorios_zypp/ /var/cache/zypp/nfs_packages nfs defaults,noauto,_netdev,nfsvers=4 0 0 which you see, specifies version 4, it can not try version 3, I believe. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHipRcACgkQtTMYHG2NR9XTOACffIW+QFKjeuKnUp+AOevz2pTk zdUAn2m01EvxVm2xK1tiMwii/N2Z0mfW =+b9W -----END PGP SIGNATURE-----