Table of Contents
Advertisement
If the removal is interrupted by a reboot and/or failover, it may be incomplete after the
switch(es) finish booting. You can re-run the command to finish removing the share.
Removing the Empty Directory Tree
Extra Processing in a Multi-Protocol Volume
CLI Maintenance Guide
The CLI prompts you with a warning before removing the share; enter yes to proceed.
The CLI blocks as the volume migrates the files and directories off of the share, then
prints a message indicating the success of the share removal.
For example, the following command removes the '/acct~it5' share from the
'wwmed' namespace, and migrates its files and master directories to the 'fm1' share
farm.
bstnA6k(gbl)# end
bstnA6k# remove-share migrate wwmed /acct it5 fm1
WARNING !! Share 'it5' will be removed from volume '/acct' in
namespace 'wwmed' after migrating files to 'fm1'
Proceed? [yes/no] yes
bstnA6k# ...
When you remove a share from a namespace, it leaves its empty directory tree on the
share's back-end filer. After removing the share, you can access the filer directly and
remove the empty directory tree.
If the share is in a multi-protocol (NFS and CIFS) volume, the volume may require
additional processing for the migration. The extra processing guards against a file or
directory on the source share colliding with a filer-generated name (FGN) at the
destination. The volume does not record filer-side FGNs in its metadata; it deduces
when collisions are possible and then uses probes to check for them.
Troubleshooting Managed Volumes
Removing an Imported Share
8-15
Advertisement
Table of Contents
Troubleshooting
