Nils Goroll wrote: > Robert, > > > I guess you could test that using proto=udp,vers=3 .. > > I had tried that, I should have mentioned that the snoop output was > for this case. Nils, it worked for me:
pnfs-18-21.root[503] mount -F nfs -o vers=3,proto=udp pnfs-18-22:/tmp/ipoib /tmp/mnt ________________________________ 11 0.03842 pnfs-18-21 -> pnfs-18-22.Central.Sun.COM ETHER Type=0800 (IP), size=174 bytes 11 0.03842 pnfs-18-21 -> pnfs-18-22.Central.Sun.COM IP D=10.1.233.224 S=10.1.233.223 LEN=160, ID=40083, TOS=0x0, TTL=255 11 0.03842 pnfs-18-21 -> pnfs-18-22.Central.Sun.COM UDP D=111 S=1023 LEN=140 11 0.03842 pnfs-18-21 -> pnfs-18-22.Central.Sun.COM RPC C XID=54799222 PROG=100000 (PMAP) VERS=2 PROC=3 11 0.03842 pnfs-18-21 -> pnfs-18-22.Central.Sun.COM PORTMAP C GETPORT prog=100021 (NLM) vers=4 proto=UDP ________________________________ 12 0.00062 pnfs-18-22.Central.Sun.COM -> pnfs-18-21 ETHER Type=0800 (IP), size=70 bytes 12 0.00062 pnfs-18-22.Central.Sun.COM -> pnfs-18-21 IP D=10.1.233.223 S=10.1.233.224 LEN=56, ID=18047, TOS=0x0, TTL=255 12 0.00062 pnfs-18-22.Central.Sun.COM -> pnfs-18-21 UDP D=1023 S=111 LEN=36 12 0.00062 pnfs-18-22.Central.Sun.COM -> pnfs-18-21 RPC R (#11) XID=54799222 Success 12 0.00062 pnfs-18-22.Central.Sun.COM -> pnfs-18-21 PORTMAP R GETPORT port=4045 ________________________________ You might need to reboot the client if the NFS was previously mounted with TCP. I think lockd caches the portmapper info and did not update it when the protocol of the mount cmd was changed. -Dai
