Re: [zones-discuss] Re: nevada zone with NAT and NFS
At least some of the servers that I can't access are using NFSv3 It has been my experience that NFSv4 on Solaris 10 and NFSv3 on other hosts, including NetApp filers, cause all sorts of problems. Either you get No Directory or the directory/files are owned by nobody. I don't know about NetApp's NFS but the latter issue can usually be resolved by setting NFSMAPID_DOMAIN on the Solaris side to tell nfsmapid(1M) what NFSv4 domain to use. You'll want to restart svc:/network/nfs/mapid after making this change. dsc ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Re: nevada zone with NAT and NFS
At least some of the servers that I can't access are using NFSv3 It has been my experience that NFSv4 on Solaris 10 and NFSv3 on other hosts, including NetApp filers, cause all sorts of problems. Either you get No Directory or the directory/files are owned by nobody. We routinely modify /etc/default/nfs and set #NFS_SERVER_VERSMAX=4 NFS_SERVER_VERSMAX=3 (or even 2) and #NFS_CLIENT_VERSMAX=4 NFS_CLIENT_VERSMAX=3 The problem goes away after you restart nfs/client or nfs/server. Ron This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
