Acopia Adaptive Resource Switch, Руководство по обслуживанию CLI

Страница: 253 / 324

Troubleshooting Managed Volumes
Correcting Share-Import Errors
CLI Maintenance Guide 8-47
Use the
remove-files migrate
command to migrate all files and directories to another
share before removing it from the volume. This command was described above; see
“Removing an Imported Share” on page 8-14 .
For example, this command sequence removes the budget share from the /acct
volume, migrating all of its files and master directories into the “bills” share:
bstnA6k(gbl)# end
bstnA6k# remove-share migrate wwmed /acct budget bills
WARNING !! Share 'budget' will be removed from volume '/acct' in
namespace 'wwmed' after migrating files to 'bills'
Proceed? [yes/no] yes
bstnA6k# ...
The share with the master instance of a directory (or master directory ) is considered the
“home” share for the directory. (Recall that a volume can have a copy of any directory in
multiple back-end shares.) This is the first-imported instance of a the directory, or
possibly the only instance. By default, the volume places any new files for the directory
into its master instance.
Removing the share ensures that none of its directories are master any longer. If the share
never returns to the volume, this is irrelevant. If you add the share back later, the volume
tends to avoid putting new files onto the share. This does not affect clients, but may
create an unexpected file distribution at the back end.
Suppose share A has two directories, “/usr” and “/log,” and you remove it from the
volume. The masters for “/usr” and “/log” migrate to another share in the volume, share
B. When share A comes back later, all new files that clients create in “/usr” and “/log”
will gravitate to share B, not share A. Only policy can cause files to move into share A.
As stated above, clients see no difference.