Acopia Networks 810-0044-00 Installationshandbuch PDF herunterladen (Seite 203)

100

101

Adding a Managed Volume

Allowing the Volume to Modify on Import

CLI Storage-Management Guide 9-9

bstnA6k(gbl-ns-vol[wwmed~/acct])# no import multi-scan

bstnA6k(gbl-ns-vol[wwmed~/acct])# ...

Safe Modes for Share Imports into Pre-Enabled Volumes

After the managed volume is fully enabled, a newly added share always uses the

multi-scan import with metadata protection. This is regardless of the volume-level

settings for

import multi-scan and/or import protection, which only apply to a full

volume import. A full volume import occurs when it is initially enabled, re-enabled

after being destaged with the Namespace Check (nsck) tool, or rebuilt with the nsck

tool. (The nsck tool is described in the CLI Maintenance Guide.)

Allowing the Volume to Modify on Import

When a managed volume imports its shares, it is possible for the shares to have

redundant filenames (for example, the /etc/hosts file could exist on two different NFS

shares). These are called file collisions, and they can prevent the import from

succeeding. The import can only succeed if you allow the volume to rename the

second file and import it with the new name. If such modifications are allowed, the

second file is renamed according to the following convention:

filename_share-jobid.ext

where

filename is the file’s original name, without its extension (for example,

“myfile” from “myfile.doc”),

share is the name of the namespace share (described below),

jobid is an integer identifying the job that imported the share, and

.ext is the file’s original extension (for example, “.doc”), if there is one.

If there is more than one redundant file, an index is added:

filename_share-jobid-index.ext

where index is a number starting at 1.

1 2 ... 198 199 200 201 202 203 204 205 206 207 208 ... 491 492

Kommentare zu diesen Handbüchern

Keine Kommentare

Acopia Networks 810-0044-00 Installationshandbuch Seite 203

Kommentare zu diesen Handbüchern