Adding a Managed Volume
Allowing the Volume to Modify on Import
CLI Storage-Management Guide 9-11
• after an import with no modify (assuming no file or directory collisions occurred
on import).
You cannot use the
modify command if the volume is in the process of importing, if
any imported shares have collisions, or if the nsck utility is being used on the volume.
Running a No-Modify Import
If you choose to import without using the modify command (to run a hypothetical
import) and there are no file collisions, you can later raise the
modify flag. This
completes the import and gives write access to clients.
You can use the shares’ import reports to find any collisions that would have
occurred. Import reports appear after the managed volume is enabled. Use
show
reports
to find all reports on the system; import reports are named
“import.share-id.share-name.job-id.rpt.” Use
show reports name to view the report.
Allowing the Volume to Modify on Re-Import
As mentioned above, the CLI Maintenance Guide describes the nsck tool for
rebuilding a managed volume. If you said “no” to the CLI prompt after you used the
modify command, nsck does not raise the modify flag after taking the volume offline.
This turns modifications off after a volume rebuild. You can use another CLI
command,
reimport-modify, to allow the modify flag to stay up after the volume is
rebuilt:
reimport-modify
This command prompts for confirmation before taking action; enter yes to proceed.
For example, this command sequence ensures that the “/acct” volume will be
modifiable after any re import:
bstnA6k(gbl)# namespace wwmed
bstnA6k(gbl-ns[wwmed])# volume /acct
bstnA6k(gbl-ns-vol[wwmed~/acct])# reimport-modify
Automatically re-enable volume modify mode during NSCK rebuild? [yes/no] yes
bstnA6k(gbl-ns-vol[wwmed~/acct])# ...
Kommentare zu diesen Handbüchern