Adding a Managed Volume
Adding a Share
9-28 CLI Storage-Management Guide
Disconnecting From the Filer Before the Share is Enabled
To correct a mistake, you can disconnect a share from its filer before you enable the
share. (The process of enabling a share is described later.) Use the
no filer command
described earlier in “Disconnecting From the Filer” on page 8-11: For example, this
command set disconnects the filer from the “spreadsheets” share:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# share spreadsheets
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~spreadsheets])# no filer
bstnA6k(gbl-ns-vol-shr[wwmed~/acct~spreadsheets])# ...
Disconnecting From the Filer After the Share 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. The CLI Maintenance Guide describes how to remove an already-imported
share without disrupting any client access to the share’s files or directories.
Setting Share-Import Options
Each managed-volume share has several options that you can set to control its import.
These subsections describe each of them in detail.
Speeding Up Import by Skipping a Directory Test
A managed volume tests each imported directory to verify that it is not already
imported into another managed volume. Two volumes cannot manage the same
directory. This managed-volume check is crucial for shares that may have been
previously imported by any ARX, so it is enabled by default. For a new filer, the first
introduction of the ARX at the site, or an nsck rebuild of the volume (described in the
CLI Maintenance Guide), you can disable this check to speed up the import of the
share. From gbl-ns-vol-shr mode, use
import skip-managed-check to skip the
directory check:
import skip-managed-check
Kommentare zu diesen Handbüchern