Installation manual

Adding a Managed Volume
Enabling the Volume
9-54 CLI Storage-Management Guide
You can use the optional take-ownership flag for this special case. If the managed
volume finds an ownership marker in the root of any of its shares, it overwrites the
marker file. Otherwise, it imports the share as usual:
enable shares take-ownership
The CLI prompts for confirmation before taking ownership of any shares. Enter yes to
proceed.
For example, the following command sequence enables all shares in the
“insur_bkup~/insurShdw” volume and takes ownership of all of them:
prtlndA1k(gbl)# namespace insur_bkup
prtlndA1k(gbl-ns[insur_bkup])# volume /insurShdw
prtlndA1k(gbl-ns-vol[insur_bkup~/insurShdw])# enable shares take-ownership
This command allows the switch to virtualize shares that are used by other Acopia switches.
Allow switch to take ownership of all the shares in this volume? [yes/no] yes
prtlndA1k(gbl-ns-vol[insur_bkup~/insurShdw])# ...
Disabling All Shares
Use no enable shares command to disable each of the volume’s individual shares.
For example, this command sequence disables all of the shares in the “ns1~/vol”
volume:
bstnA6k(gbl)# namespace ns1
bstnA6k(gbl-ns[ns1])# volume /vol
bstnA6k(gbl-ns-vol[ns1~/vol])# no enable shares
bstnA6k(gbl-ns-vol[ns1~/vol])# ...
Do not use this option if it is possible that another ARX is managing one of the volume’s
shares. This would unexpectedly remove the share(s) from service at the other ARX.
This is equivalent to disabling the volume, described below. This causes the volume to
stop responding to clients; different client applications react to this in different ways.
Some may hang, others may log errors that are invisible to the end user.