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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Name<br />

mmcrnsd – Creates cluster-wide names for Network Shared Disks (NSDs) used by <strong>GPFS</strong>.<br />

Synopsis<br />

mmcrnsd -F DescFile [-v {yes |no}]<br />

Description<br />

The mmcrnsd comm<strong>and</strong> is used to create cluster-wide names for NSDs used by <strong>GPFS</strong>.<br />

This is the first <strong>GPFS</strong> step in preparing a disk for use by a <strong>GPFS</strong> file system. A disk descriptor file<br />

supplied to this comm<strong>and</strong> is rewritten with the new NSD names <strong>and</strong> that rewritten disk descriptor file can<br />

then be supplied as input to the mmcrfs, mmadddisk or mmrpldisk comm<strong>and</strong>s.<br />

The name created by the mmcrnsd comm<strong>and</strong> is necessary since disks connected at multiple nodes may<br />

have differing disk device names in /dev on each node. The name uniquely identifies the disk. This<br />

comm<strong>and</strong> must be run for all disks that are to be used in <strong>GPFS</strong> file systems. The mmcrnsd comm<strong>and</strong> is<br />

also used to assign a primary <strong>and</strong> backup NSD server that can be used for I/O operations on behalf of<br />

nodes that do not have direct access to the disk.<br />

To identify that the disk has been processed by the mmcrnsd comm<strong>and</strong>, a unique NSD volume ID is<br />

written on sector 2 of the disk. All of the NSD comm<strong>and</strong>s (mmcrnsd, mmlsnsd, <strong>and</strong> mmdelnsd) use this<br />

unique NSD volume ID to identify <strong>and</strong> process NSDs.<br />

After the NSDs are created, the <strong>GPFS</strong> cluster data is updated <strong>and</strong> they are available for use by <strong>GPFS</strong>.<br />

When using an IBM Eserver High Performance Switch (HPS) in your configuration, it is suggested you<br />

process your disks in two steps:<br />

1. Create virtual shared disks on each physical disk through the mmcrvsd comm<strong>and</strong>.<br />

2. Using the rewritten disk descriptors from the mmcrvsd comm<strong>and</strong>, create NSDs through the mmcrnsd<br />

comm<strong>and</strong>.<br />

Results<br />

Upon successful completion of the mmcrnsd comm<strong>and</strong>, these tasks are completed:<br />

v NSDs are created.<br />

v The DescFile contains NSD names to be used as input to the mmcrfs, mmadddisk, or the mmrpldisk<br />

comm<strong>and</strong>s.<br />

v A unique NSD volume ID to identify the disk as an NSD has been written on sector 2.<br />

v An entry for each new disk is created in the <strong>GPFS</strong> cluster data.<br />

Parameters<br />

-F DescFile<br />

The file containing the list of disk descriptors, one per line. Disk descriptors have this format:<br />

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

DiskName<br />

The block device name appearing in /dev for the disk you want to define as an NSD.<br />

Examples of disks accessible through a block device are SAN-attached disks or virtual<br />

shared disks. If a PrimaryServer node is specified, DiskName must be the /dev name for<br />

the disk device on the primary NSD server node. See the Frequently Asked Questions at<br />

126 <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!