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.

mmfsctl Comm<strong>and</strong><br />

Name<br />

mmfsctl – Issues a file system control request.<br />

Synopsis<br />

mmfsctl Device {suspend | resume}<br />

Or,<br />

mmfsctl Device {exclude | include} {-d ″DiskName[;DiskName...]″ | -F DiskFile | -G FailureGroup}<br />

Or,<br />

mmfsctl Device syncFSconfig {-n RemoteNodesFile | -C remoteClusterName} [-S SpecFile]<br />

Description<br />

Use the mmfsctl comm<strong>and</strong> to issue control requests to a particular <strong>GPFS</strong> file system. The comm<strong>and</strong> is<br />

used to temporarily suspend the processing of all application I/O requests, <strong>and</strong> later resume them, as well<br />

as to synchronize the file system’s configuration state between peer clusters in disaster recovery<br />

environments.<br />

See Establishing disaster recovery for your <strong>GPFS</strong> cluster in General Parallel File System: Advanced<br />

<strong>Administration</strong> Guide.<br />

Before creating a FlashCopy ®<br />

image of the file system, the user must run mmfsctl suspend to<br />

temporarily quiesce all file system activity <strong>and</strong> flush the internal buffers on all nodes that mount this file<br />

system. The on-disk metadata will be brought to a consistent state, which provides for the integrity of the<br />

FlashCopy snapshot. If a request to the file system is issued by the application after the invocation of this<br />

comm<strong>and</strong>, <strong>GPFS</strong> suspends this request indefinitely, or until the user issues mmfsctl resume.<br />

Once the FlashCopy image has been taken, the mmfsctl resume comm<strong>and</strong> can be issued to resume the<br />

normal operation <strong>and</strong> complete any pending I/O requests.<br />

The mmfsctl syncFSconfig comm<strong>and</strong> extracts the file system’s related information from the local <strong>GPFS</strong><br />

configuration data, transfers this data to one of the nodes in the peer cluster, <strong>and</strong> attempts to import it<br />

there.<br />

Once the <strong>GPFS</strong> file system has been defined in the primary cluster, users run this comm<strong>and</strong> to import the<br />

configuration of this file system into the peer recovery cluster. After producing a FlashCopy image of the<br />

file system <strong>and</strong> propagating it to the peer cluster using Peer-to-Peer Remote Copy (PPRC), users similarly<br />

run this comm<strong>and</strong> to propagate any relevant configuration changes made in the cluster after the previous<br />

snapshot.<br />

The primary cluster configuration server of the peer cluster must be available <strong>and</strong> accessible using remote<br />

shell <strong>and</strong> remote copy at the time of the invocation of the mmfsctl syncFSconfig comm<strong>and</strong>. Also, the<br />

peer <strong>GPFS</strong> clusters should be defined to use the same remote shell <strong>and</strong> remote copy mechanism, <strong>and</strong><br />

they must be set up to allow nodes in peer clusters to communicate without the use of a password.<br />

Not all administrative actions performed on the file system necessitate this type of resynchronization. It is<br />

required only for those actions that modify the file system information maintained in the local <strong>GPFS</strong><br />

configuration data, which includes:<br />

v Additions, removals, <strong>and</strong> replacements of disks (comm<strong>and</strong>s mmadddisk, mmdeldisk, mmrpldisk)<br />

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

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

Saved successfully!

Ooh no, something went wrong!