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.

mmcrnsd Comm<strong>and</strong><br />

Note: This name can contain only the following characters: ’A’ through ’Z’, ’a’ through ’z’,<br />

’0’ through ’9’, or ’_’ (the underscore). All other characters are not valid.<br />

If a desired name is not specified, the NSD is assigned a name according to the<br />

convention:<br />

gpfsNNnsd where NN is a unique nonnegative integer not used in any prior NSD.<br />

StoragePool<br />

Specifies the name of the storage pool that the NSD is assigned to. This field is ignored<br />

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

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

Upon successful completion of the mmcrnsd comm<strong>and</strong>, the DescFile file is rewritten to contain the<br />

created NSD names in place of the device name. Primary <strong>and</strong> backup NSD servers <strong>and</strong> desiredName are<br />

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

The original lines, as well as descriptor lines in error, are commented out <strong>and</strong> preserved for reference. The<br />

rewritten disk descriptor file can then be used as input to the mmcrfs, mmadddisk, or the mmrpldisk<br />

comm<strong>and</strong>s. You must have write access to the directory where the DescFile file is located in order to<br />

rewrite the created NSD information.<br />

The Disk Usage <strong>and</strong> Failure Group specifications in the disk descriptor are preserved only if you use the<br />

rewritten file produced by the mmcrnsd comm<strong>and</strong>. If you do not use this file, you must either accept the<br />

default values or specify new values when creating disk descriptors for other comm<strong>and</strong>s.<br />

Options<br />

-v {yes |no}<br />

Verify the disk is not already formatted as an NSD.<br />

A value of -v yes specifies that the NSD are to be created only if the disk has not been formatted<br />

by a previous invocation of the mmcrnsd comm<strong>and</strong>, as indicated by the NSD volume ID on sector<br />

2 of the disk. A value of -v no specifies that the disk is to be formatted irrespective of its previous<br />

state. The default is -v yes.<br />

Exit status<br />

0 Successful completion.<br />

nonzero A failure has occurred.<br />

Security<br />

You must have root authority to run the mmcrnsd comm<strong>and</strong>.<br />

You may issue the mmcrnsd comm<strong>and</strong> from any node in the <strong>GPFS</strong> cluster.<br />

When using the rcp <strong>and</strong> rsh comm<strong>and</strong>s for remote communication, a properly configured .rhosts file must<br />

exist in the root user’s home directory, on each node in the <strong>GPFS</strong> cluster. If you have designated the use<br />

of a different remote communication program on either the mmcrcluster or the mmchcluster comm<strong>and</strong>,<br />

you must ensure:<br />

1. Proper authorization is granted to all nodes in the <strong>GPFS</strong> cluster.<br />

2. The nodes in the <strong>GPFS</strong> cluster can communicate without the use of a password, <strong>and</strong> without any<br />

extraneous messages.<br />

Examples<br />

To create your NSDs from the descriptor file nsdesc containing:<br />

128 <strong>GPFS</strong>: <strong>Administration</strong> <strong>and</strong> <strong>Programming</strong> <strong>Reference</strong>

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

Saved successfully!

Ooh no, something went wrong!