Installation manual

Configuring Front-End Services
Configuring CIFS
CLI Storage-Management Guide 11-21
Adding New Subshares
This section only applies to managed volumes. Skip to the next section if you are
sharing a direct volume.
The previous sections explained how to export pre-existing subshares, created on the
back-end filers before their CIFS shares were imported. To add new subshares, you
must directly connect to one of the back-end filers and create them there; a volume
manages files and directories, but does not manage share definitions or ACLs.
Once the subshares and their ACLs are created on one filer, you can use the priv-exec
sync shares command to find them, duplicate them on all other filers, and make the
managed volume aware of them. Then you can use the commands described above to
export the new subshares from the front-end CIFS service. The sync utility is
described in CLI Maintenance Guide; for details on the
sync shares command, see
“Adding and Synchronizing Filer Subshares (CIFS)” on page 5-30.
Stopping a CIFS Share
Use the no form of the export command to stop CIFS access to a namespace volume:
no export namespace volume [as share-name]
where
namespace (1-30 characters) is the namespace containing the CIFS share,
volume (1-1024 characters) is the name of a current CIFS share (for
example, “alpha”), and
as share-name (optional, 1-1024 characters) stops access via the specified
share name. If the volume is exported under more than one share name, the
share is still supported under the remaining names.
For example, the following command sequence stops the CIFS server at
ac1.medarch.org from sharing the “/cifstest” volume in the “medarcv” namespace:
This is contrary to standard best practices; direct access to the shares behind a managed
volume can easily corrupt the volume’s metadata. This exception is for new CIFS
subshares only.