Installation manual

Adding a Managed Volume
Adding a Share
CLI Storage-Management Guide 9-25
Disabling Filer Subshares
From gbl-ns-vol mode, use the no filer-subshares command to disable volume support
for CIFS subshares and their share-level ACLs:
no filer-subshares
You can only disable this feature when no CIFS services are sharing any of the
volume’s subshares. CIFS front-end services are described in a later chapter, along
with instructions on sharing CIFS subshares.
For example, this command sequence prevents CIFS-subshare support in the
“insur~/claims” volume:
bstnA6k(gbl)# namespace insur
bstnA6k(gbl-ns[insur])# volume /claims
bstnA6k(gbl-ns-vol[insur~/claims])# no filer-subshares
bstnA6k(gbl-ns-vol[insur~/claims])# ...
Adding a Share
The next step in creating a managed volume is identifying one or more shares for it. A
share is one CIFS share or NFS export from an external (NAS or DAS) filer. A
volume can contain multiple shares, where each typically resides on a different filer.
As with direct volumes, you use the
share command to add a share to a managed
volume. This puts you into gbl-ns-vol-shr mode, where you must identify the filer and
export/share, and then you must enable the share. A managed-volume share also has
several options related to import.
The first configured share in a managed volume, by default, will hold all new files
created in the volume’s root. The volume’s root is the volume’s top-most directory (for
example, /acct). The share is called the root-backing share for the volume. Choose the
root-backing share carefully, as it could possibly be overburdened by new files from
clients.
To ease this burden, you can configure a share farm to distribute new files among
multiple shares. You will learn how to configure these policies in a later chapter.