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.

v You must identify the disks by the NSD names that were given to them by the mmcrnsd comm<strong>and</strong>.<br />

v You must explicitly specify values for both the primary <strong>and</strong> backup NSD server nodes even if you are<br />

only changing one of them.<br />

v The file system that contains the NSD being changed must be unmounted prior to issuing the<br />

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

v The NSD must be properly connected to the new nodes prior to issuing the mmchnsd comm<strong>and</strong>.<br />

v This comm<strong>and</strong> cannot be used to change the DiskUsage or FailureGroup for an NSD. You must issue<br />

the mmchdisk comm<strong>and</strong> to change these.<br />

v You cannot change the name of the NSD.<br />

For example, to assign node k145n07 as a backup NSD server for disk gpfs47nsd:<br />

1. Since you must always specify the primary, first issue the mmlsnsd comm<strong>and</strong> to ensure you are not<br />

inadvertently changing the primary server.<br />

mmlsnsd -d "gpfs47nsd"<br />

The system displays information similar to:<br />

File system Disk name Primary node Backup node<br />

---------------------------------------------------------------<br />

fs1 gpfs47nsd k145n06<br />

2. Unmount the file system on all nodes <strong>and</strong> ensure that the disk is connected to the new node k145n07.<br />

3. Next issue the mmchnsd comm<strong>and</strong>:<br />

mmchnsd "gpfs47nsd:k145n06:k145n07"<br />

4. Verify the changes by issuing the mmlsnsd comm<strong>and</strong>:<br />

mmlsnsd -d "gpfs47nsd"<br />

The system displays information similar to:<br />

File system Disk name Primary node Backup node<br />

---------------------------------------------------------------<br />

fs1 gpfs47nsd k145n06 k145n07<br />

Changing NSD server usage <strong>and</strong> failback<br />

<strong>GPFS</strong> determines if a node has physical or virtual connectivity to an underlying NSD disk through a<br />

sequence of comm<strong>and</strong>s invoked from the <strong>GPFS</strong> daemon. This determination is called disk discovery <strong>and</strong><br />

occurs at both initial <strong>GPFS</strong> startup as well as whenever a file system is mounted.<br />

The default order of access used in disk discovery:<br />

1. Local /dev block device interfaces for virtual shared disk, SAN, SCSI or IDE disks<br />

2. NSD servers<br />

The useNSDserver file system mount option can be used to set the order of access used in disk<br />

discovery, <strong>and</strong> limit or eliminate switching from local access to NSD server access, or the other way<br />

around. This option is specified using the -o flag of the mmmount, mount, mmchfs, <strong>and</strong> mmremotefs<br />

comm<strong>and</strong>s, <strong>and</strong> has one of these values:<br />

always Always access the disk using the NSD server.<br />

asfound Access the disk as found (the first time the disk was accessed). No change of disk access<br />

from local to NSD server, or the other way around, is performed by <strong>GPFS</strong>.<br />

asneeded Access the disk any way possible. This is the default.<br />

never Always use local disk access.<br />

For example, to always use the NSD server when mounting file system fs1, issue this comm<strong>and</strong>:<br />

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