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.

mmexportfs Comm<strong>and</strong><br />

Name<br />

mmexportfs - Retrieves the information needed to move a file system to a different cluster.<br />

Synopsis<br />

mmexportfs {Device | all} -o ExportFilesysData<br />

Description<br />

The mmexportfs comm<strong>and</strong>, in conjunction with the mmimportfs comm<strong>and</strong>, can be used to move one or<br />

more <strong>GPFS</strong> file systems from one <strong>GPFS</strong> cluster to another <strong>GPFS</strong> cluster, or to temporarily remove file<br />

systems from the cluster <strong>and</strong> restore them at a later time. The mmexportfs comm<strong>and</strong> retrieves all<br />

relevant file system <strong>and</strong> disk information <strong>and</strong> stores it in the file specified with the -o parameter. This file<br />

must later be provided as input to the mmimportfs comm<strong>and</strong>. When running the mmexportfs comm<strong>and</strong>,<br />

the file system must be unmounted on all nodes.<br />

When all is specified in place of a file system name, any disks that are not associated with a file system<br />

will be exported as well.<br />

Exported file systems remain unusable until they are imported back with the mmimportfs comm<strong>and</strong> to the<br />

same or a different <strong>GPFS</strong> cluster.<br />

Results<br />

Upon successful completion of the mmexportfs comm<strong>and</strong>, all configuration information pertaining to the<br />

exported file system <strong>and</strong> its disks is removed from the configuration data of the current <strong>GPFS</strong> cluster <strong>and</strong><br />

is stored in the user specified file ExportFilesysData.<br />

Parameters<br />

Device | all<br />

The device name of the file system to be exported. File system names need not be fully-qualified.<br />

fs0 is as acceptable as /dev/fs0. Specify all to export all <strong>GPFS</strong> file systems, as well as all disks<br />

that do not belong to a file system yet. This must be the first parameter.<br />

-o ExportFilesysData<br />

The path name of a file to which the file system information is to be written. This file must be<br />

provided as input to the subsequent mmimportfs comm<strong>and</strong>.<br />

Exit status<br />

0 Successful completion.<br />

nonzero A failure has occurred.<br />

Security<br />

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

You may issue the mmexportfs 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 mmchcluster comm<strong>and</strong>, you<br />

must ensure:<br />

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

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