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

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

Troubleshooting Managed Volumes
Correcting Share-Import Errors
8-46 CLI Maintenance Guide
If the import failed during the scan of the back-end filer, the managed volume did not
change any of its metadata for the share. In this case, it should be enough to disable
the share (with
no enable
in gbl-ns-vol-shr mode) and then re-enable it. For details on
enabling and disabling a share in a managed volume, refer to “Enabling the Share” on
page 9-40 of the CLI Storage-Management Guide .
For example, this command sequence successfully restarts an import for the
wwmed~/acct~budget share:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# share budget
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~budget])# no enable
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~budget])# enable
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~budget])# ...
If this method fails, metadata was probably written before the import failed. You can
try one of the alternatives described below.
Removing the Share from the Volume
You can remove the volume from the share as a first step to retrying the import, or as
a final step.
Any imported directories and files are visible to the volume’s clients, so you begin by
choosing how to handle them. You can migrate all files and directories to other shares
in the volume, migrate only the directories, or remove all of the share’s files and
directories. The sections below describe each of these options.
The entire volume fails if its metadata share fails or its only share fails. In either of
these cases, you must rebuild the entire volume; skip to the next section for this
situation.
Retaining Both Directories and Files in the Volume
If any files were imported from the share, you can migrate them elsewhere in the
volume before the share is removed. The files move along with the share’s master
directories. No files remain on the share after this process is over.