Installation manual

Adding a Managed Volume
Adding a Share
9-44 CLI Storage-Management Guide
Disabling the Share
You can disable a share to make it inaccessible to namespace clients. This stops
access to all files on the share. As in a direct volume, use
no enable in gbl-ns-vol-shr
mode to disable the share.
Removing a Managed-Volume Share
You can easily remove a share before its volume is first enabled and starts importing
files. Use
no share in this case, just as describe for a share in a direct volume. For
example, this command set removes the “billsBU” share from the “/acct” volume in
the “wwmed” namespace:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# no share billsBU
bstnA6k(gbl-ns-vol[wwmed~/acct])# ...
Removing the Share After it is Enabled
After you enable the share, it has files and directories that were imported from the
filer. That is, files and directories were scanned and incorporated into the volume’s
metadata. These files are visible to the volume’s clients, and cannot be removed
without disrupting client service. A client-friendly approach is to migrate the files to
other shares in the same volume; clients can access the files throughout the migration.
The CLI Maintenance Guide explains how to migrate all the files and remove an
imported share with a single command (see “Removing an Imported Share” on
page 8-14 of that manual).
This suspends all policy rules in the current volume; the rules are enabled, but not
enforced. To bring policy back online for the current volume, remove the share
(described below) or re-enable it.