Installation manual

Adding a Direct Volume
Adding a Share
CLI Storage-Management Guide 8-7
bstnA6k(gbl)# namespace medarcv
bstnA6k(gbl-ns[medarcv])# volume /test_results
bstnA6k(gbl-ns-vol[medarcv~/test_results])# cifs oplocks-disable auto
bstnA6k(gbl-ns-vol[medarcv~/test_results])# ...
Reinstating Oplock Support
Use no cifs oplocks-disable to support CIFS oplocks in the current volume:
no cifs oplocks-disable
For example, the following command sequence enables oplocks in the “medco~/vol”
volume:
bstnA6k(gbl)# namespace medco
bstnA6k(gbl-ns[medco])# volume /vol
bstnA6k(gbl-ns-vol[medco~/vol])# no cifs oplocks-disable
bstnA6k(gbl-ns-vol[medco~/vol])# ...
Adding a Share
The next step in creating a direct volume is identifying one or more shares for it. A
share maps to a single CIFS share or NFS export from an external (NAS or DAS)
filer. A direct share contains one or more attach-point directories, each attached to a
real directory on its back-end share. A direct volume can contain dozens of shares,
where each could possibly correspond to a different filer.
From gbl-ns-vol mode, use the
share command to add a share to a volume:
share name
where name (1-64 characters) is a name you choose for the new share.
As with new namespaces and volumes, the CLI prompts for confirmation before
creating a new share. Enter yes to proceed. This puts you into gbl-ns-vol-shr mode,
where you must identify the filer and export/share, and then you must enable the
namespace share.
For example, this command set adds a share called “corporate” to the “/vol” volume
in the “medco” namespace: