-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20/09/12 11:59, Guillaume Rousse wrote: > Le 20/09/2012 11:54, Anne Wilson a écrit : >>> and -v option to mount.nfs on client side to get more verbose >>> error reporting. >>> >> >> How do I do that? mount.nfs is an executable, not a shell >> script, so I can't add it there. Attempting to add it in the >> mount command says it is an invalid option. > This is probably an issue with arguments order in command line > parsing. Try either of those command (they are strictly > equivalent): mount -v -t nfs 192.168.0.40:/Data1 /mnt/borg2_Data1
mount -v -t nfs 192.168.0.40:/Data1 /mnt/borg2_Data1 mount.nfs: timeout set for Thu Sep 20 13:54:21 2012 mount.nfs: trying text-based options 'vers=4,addr=192.168.0.40,clientaddr=192.168.0.20' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'addr=192.168.0.40' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: requested NFS version or transport protocol is not supported > mount.nfs -v 192.168.0.40:/Data1 /mnt/borg2_Data1 > mount.nfs -v 192.168.0.40:/Data1 /mnt/borg2_Data1 mount.nfs: timeout set for Thu Sep 20 13:55:36 2012 mount.nfs: trying text-based options 'vers=4,addr=192.168.0.40,clientaddr=192.168.0.20' mount.nfs: mount(2): Protocol not supported mount.nfs: trying text-based options 'addr=192.168.0.40' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=2, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: requested NFS version or transport protocol is not supported > If that doesn't work, check their man page for exact syntax. > > Also, you can check available NFS version on your servers: rpcinfo > -s 192.168.0.40 rpcinfo -s 192.168.0.40 program version(s) netid(s) service owner 100000 2,3,4 local,udp,tcp,udp6,tcp6 portmapper superuser 100024 1 tcp6,udp6,tcp,udp status superuser 100021 4,3,1 tcp6,udp6,tcp,udp nlockmgr superuser 100003 4,3,2 udp6,tcp6 nfs superuser 100227 3,2 udp6,tcp6 nfs_acl superuser 100005 3,2,1 tcp6,udp6,tcp,udp mountd superuser Doesn't mean much to me :-( > rpcinfo -s 192.168.0.200 > Doesn't reply - presumably firewalled. Looks as though the problem relates to rpc on the server. I don't mind doing the digging, but can you point me to the right place to start the hole? Anne - -- Need KDE help? Try http://userbase.kde.org or http://forum.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBbE2IACgkQj93fyh4cnBeVagCfVPOT1IGe3rPpS3kz+gigRhtE dyUAn3AENy9iikO+l6uss6vjqxbFFpSm =/t2/ -----END PGP SIGNATURE-----