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.

publib.boulder.ibm.com/infocenter/clresctr/topic/com.ibm.cluster.gpfs.doc/<br />

gpfs_faqs/gpfsclustersfaq.html for the latest supported disk types.<br />

<strong>GPFS</strong> provides the mmcrvsd helper comm<strong>and</strong> to ease configuration of /dev disk devices.<br />

In an AIX environment, this comm<strong>and</strong> can be used to configure virtual shared disks <strong>and</strong><br />

make them accessible to nodes connected over a high performance switch. The output<br />

disk descriptor file from an mmcrvsd comm<strong>and</strong> can be used as input to the mmcrnsd<br />

comm<strong>and</strong>, since the virtual shared disk names enumerated in that file will appear as /dev<br />

block devices on switch attached nodes.<br />

PrimaryServer<br />

The name of the primary NSD server node.<br />

If this field is omitted, the disk is assumed to be SAN-attached to all nodes in the cluster. If<br />

not all nodes in the cluster have access to the disk, or if the file system to which the disk<br />

belongs is to be accessed by other <strong>GPFS</strong> clusters, PrimaryServer must be specified.<br />

BackupServer<br />

The name of the backup NSD server node.<br />

If the PrimaryServer has been specified <strong>and</strong> this field is omitted, it is assumed you do not<br />

want failover in the event that the PrimaryServer fails. If BackupServer is specified <strong>and</strong> the<br />

PrimaryServer has not been specified, the comm<strong>and</strong> fails.<br />

For general information on how to specify node names, see “Specifying nodes as input to<br />

<strong>GPFS</strong> comm<strong>and</strong>s” on page 4.<br />

DiskUsage<br />

Specify a disk usage or accept the default. This field is ignored by the mmcrnsd<br />

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

mmcrnsd comm<strong>and</strong>. Possible values are:<br />

dataAndMetadata<br />

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

dataOnly<br />

Indicates that the disk contains data <strong>and</strong> does not contain metadata.<br />

metadataOnly<br />

Indicates that the disk contains metadata <strong>and</strong> does not contain data.<br />

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

descOnly<br />

Indicates that the disk contains no data <strong>and</strong> no file metadata. Such a disk is used<br />

solely to keep a copy of the file system descriptor, <strong>and</strong> can be used as a third<br />

failure group in certain disaster recovery configurations. For more information, see<br />

General Parallel File System: Advanced <strong>Administration</strong> <strong>and</strong> search on<br />

Synchronous mirroring utilizing <strong>GPFS</strong> replication.<br />

FailureGroup<br />

A number identifying the failure group to which this disk belongs. You can specify any<br />

value from -1 (where -1 indicates that the disk has no point of failure in common with any<br />

other disk) to 4000. If you do not specify a failure group, the value defaults to the NSD<br />

primary server node number plus 4000. If an NSD server node is not specified, the value<br />

defaults to -1.<br />

<strong>GPFS</strong> uses this information during data <strong>and</strong> metadata placement to assure that no two<br />

replicas of the same block are written in such a way as to become unavailable due to a<br />

single failure. All disks that are attached to the same NSD server or adapter should be<br />

placed in the same failure group.<br />

DesiredName<br />

Specify the name you desire for the NSD to be created. This name must not already be<br />

used as another <strong>GPFS</strong> disk name, <strong>and</strong> it must not begin with the reserved string ’gpfs’.<br />

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

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

Saved successfully!

Ooh no, something went wrong!