> From: Jonathan Adams [mailto:[email protected]] > Sent: Thursday, January 30, 2014 4:06 AM > > If a share was mounted on the client and you change the underlying NFS > version on the server then you will need to get the client to unmount all > shares from the server before they can see the version 3 shares ... is this > the case in your instance? > > Are your shares auto-mounted? if so it depends on which system you're > using > but it might be quicker to reboot ... :(
For now, I'm just trying to make it work. Later I can make it automount or whatever, so at present, it goes like this: (On server) sudo zfs set [email protected]/32,[email protected]/32 storage/ad1 (on ubuntu 10.04 client) root@orion:~# mount -v -t nfs storage1:/storage/ad1 /mnt mount.nfs: timeout set for Thu Jan 30 09:01:24 2014 mount.nfs: text-based options: 'addr=10.10.10.13' mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed Since that didn't work, I try with ESXi 5.5 client, I repeat, eliminating the @ symbols, eliminating the /32, and putting them back in there... Set the versions as follows: sudo sharectl set -p server_versmax=3 nfs sudo svcadm refresh svc:/network/nfs/server:default Retry all the variations of set sharenfs and repeat trying to mount... Still nothing works... I wondered if maybe I have firewall enabled on the server. So I used "nc" and "telnet" from the client to confirm the port is open. (111 and 2049). No problem. The only thing that *does* work: When I have the 151a7 box mount the 151a9 box using nfs v4, then it works. But if I reduce the server and client both to v3, then even THEY fail to mount too. _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
