29.01.2013 Views

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

v The primary server is configured <strong>and</strong> the volume group is varied online there.<br />

v The backup server is configured <strong>and</strong> the volume group is imported there, but varied off.<br />

v The DescFile file is rewritten to contain the created virtual shared disk names in place of any disk<br />

descriptors containing physical disk or vpath names. Primary <strong>and</strong> backup servers are omitted from the<br />

rewritten disk descriptor <strong>and</strong> all other fields, if specified, are copied without modification. The rewritten<br />

disk descriptor file can then be used as input to the mmcrnsd comm<strong>and</strong>.<br />

Error recovery<br />

Each step of the mmcrvsd process is enumerated during comm<strong>and</strong> execution. For example at step 0, the<br />

mmcrvsd comm<strong>and</strong> prints:<br />

Step 0: Setting up environment<br />

As each step is started, its corresponding number is recorded in the DescFile file as a comment at the<br />

end. This comment serves as restart information to subsequent invocations of the mmcrvsd comm<strong>and</strong>.<br />

For example at step one, the recorded comment would be:<br />

#MMCRVSD_STEP=0<br />

Upon failure, appropriate error messages from the failing system component are displayed along with<br />

mmcrvsd error messages.<br />

After correcting the failing condition <strong>and</strong> restarting the mmcrvsd comm<strong>and</strong> with the same descriptor file,<br />

the comm<strong>and</strong> prompts you to restart at the last failing step. For example, if a prior invocation of mmcrvsd<br />

failed at step one, the prompt would be:<br />

A prior invocation of this comm<strong>and</strong> has recorded a partial<br />

completion in the file (/tmp/DescFile).<br />

Should we restart at prior failing step(1)?[y]/n=><br />

The default response is y; yes restart at the prior failing step.<br />

Parameters<br />

-F DescFile<br />

The file containing the list of disk descriptors, one per line, in the form:<br />

DiskName:PrimaryServer:BackupServer:DiskUsage:FailureGroup:DesiredName:StoragePool<br />

mmcrvsd Comm<strong>and</strong><br />

DiskName<br />

The device name of the disk you want to use to create a virtual shared disk. This can be<br />

either an hdisk name or a vpath name for an SDD device. <strong>GPFS</strong> performance <strong>and</strong><br />

recovery processes function best with one disk per virtual shared disk. If you want to<br />

create virtual shared disks with more than one disk, refer to the correct manual for your<br />

environment at: publib.boulder.ibm.com/clresctr/windows/public/rsctbooks.html<br />

PrimaryServer<br />

The name of the virtual shared disk server node. This can be in any recognizable form.<br />

BackupServer<br />

The backup server name. This can be specified in any recognizable form or allowed to<br />

default to none.<br />

Disk Usage<br />

Specify a disk usage or accept the default (see General Parallel File System: Concepts,<br />

Planning, <strong>and</strong> Installation Guide <strong>and</strong> search on recoverability considerations). This field is<br />

ignored by the mmcrvsd comm<strong>and</strong> <strong>and</strong> is passed unchanged to the output descriptor file<br />

produced by the mmcrvsd comm<strong>and</strong>.<br />

dataAndMetadata<br />

Indicates that the disk contains both data <strong>and</strong> metadata. This is the default.<br />

Chapter 8. <strong>GPFS</strong> comm<strong>and</strong>s 135

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!