Tuning the MVFS cache for a non-global zone using cleartool setcache
The cleartool setcache command has a -zone option that allows you to specify the MVFS cache size for a particular zone.
About this task
In addition to specifying mvfs_expected_zone_count, you can override the automatically computed values for a given zone by setting the scaling factor and cache sizes in that zone using the cleartool setcache -zone command from the global zone.
To tune the MVFS performance for a non-global zone using the cleartool setcache command, use the following procedure.
Procedure
- Log on to the global zone as root.
- For each non-global zone, create a directory in the global
zone that contains the configuration information for the non-global
zone.
mkdir -p /var/adm/hcl/versionvault/mvfsconfig/zone/ngz-name
- Following the commented example below as a guide, use the Solaris zonecfg utility to map that directory to the non-global zone's file system hierarchy.
- For each non-global zone for which you want to tune the
MVFS cache, specify the MVFS tuning parameters using the cleartool setcache command:
Example
#In this example, the zone that is to be configured is daystar-5
mkdir -p /var/adm/hcl/versionvault/mvfsconfig/zone/nleidc307
zonecfg -z daystar-z5
#Use the zonecfg sub-application "fs" to add a filesystem
zonecfg:daystar-z5> add fs
#Within the fs sub-application, set the directory, specifying an absolute path (symbolic links are not supported)
zonecfg:daystar-z5:fs> set dir=/var/adm/hcl/versionvault/mvfsconfig
#Specify the mount point as special
zonecfg:daystar-z5:fs> set special=/var/adm/hcl/versionvault/mvfsconfig/zone/my_ngz_zone
#Set the file system type to lofs (loop-back)
zonecfg:daystar-z5:fs> set type=lofs
#Set to read-only and disallow opening of device-special files
zonecfg:daystar-z5:fs> add options [ro,nodevices]
#Now exit the fs sub-application
zonecfg:daystar-z5:fs> end
#Verify and commit the changes
zonecfg:daystar-z5> verify
zonecfg:daystar-z5> commit
#Exit the zonecfg utility
zonecfg:daystar-z5> exit