Using explicit NFS mounts
For safest behavior (not subject to autofs- or automount-induced failures), use explicit file system mounts to make the VOB storage available on the VOB server host.
Following are sample commands for mounting a filer's NFSv4 export and checking that you can view NFSv4 ACLs. If you get an error viewing ACLs, verify the mount options and the filer configuration before proceeding with the VOBs.
After you validate that the NFSv4 mount is correct, add a permanent mount-point entry to the file system table to be mounted when the system boots.
Linux™
SUSE Linux Enterprise: you must be running SLES 11 or higher to use ACLs-enabled VOBs stored on a filer.
Red Hat Enterprise Linux: all versions supported by HCL VersionVault also support ACLs-enabled VOBs stored on a filer.
mount -t nfs4 filer:/ /nfs4-filer
ls -ld /nfs4-filer/vol/cc_acl_nfsv4/stg
nfs4_getfacl /nfs4-filer/vol/cc_acl_nfsv4/stgSolaris 11
mount -o vers=4 filer:/ /nfs4-filer
ls -ld /nfs4-filer/vol/cc_acl_nfsv4/stg
ls -Vd /nfs4-filer/vol/cc_acl_nfsv4/stgEnsure the ls -Vd output includes a "deny" line, which is an indication that NFSv4 ACLs are working. Alternatively, you can use chmod to add an access control entry to a file's ACL and verify that succeeds.
Solaris 10
The Solaris 10 NFS client does not support server volume mount-point crossing. For a Solaris 10 VOB server, you must mount the storage volume explicitly instead of the root. Note that this means the host-local path omits the /vol/volume-name portion of the path, unlike the other UNIX™ variants.
mount -o vers=4 filer:/vol/cc_acl_nfsv4 /nfs4-filer
ls -ld /nfs4-filer/stg
ls -Vd /nfs4-filer/stgCheck the output as described for Solaris 11.