source: gpfs_3.1_ker2.6.20/share/man/man8/mmexportfs.8 @ 219

.TH mmexportfs 02/16/06
mmexportfs Command
.SH "Name"
.PP
\fBmmexportfs\fR - Retrieves the information needed to move a file system
to a different cluster.
.SH "Synopsis"
.PP
\fBmmexportfs\fR {\fIDevice\fR | \fBall\fR} \fB-o\fR
\fIExportFilesysData\fR
.SH "Description"
.PP
The \fBmmexportfs\fR command, in conjunction with the \fBmmimportfs\fR command, can be used to move one or more
GPFS file systems from one GPFS cluster to another GPFS cluster, or to
temporarily remove file systems from the cluster and restore them at a later
time. The \fBmmexportfs\fR command retrieves all relevant file
system and disk information and stores it in the file specified with the
\fB-o\fR parameter. This file must later be provided as input to the
\fBmmimportfs\fR command. When running the
\fBmmexportfs\fR command, the file system must be unmounted on all
nodes.
.PP
When \fBall\fR is specified in place of a file system name, any disks
that are not associated with a file system will be exported as well.
.PP
Exported file systems remain unusable until they are imported back with the
\fBmmimportfs\fR command to the same or a different
GPFS cluster.
.SH "Results"
.PP
Upon successful completion of the \fBmmexportfs\fR command, all
configuration information pertaining to the exported file system and its disks
is removed from the configuration data of the current GPFS cluster and is
stored in the user specified file \fIExportFilesysData\fR.
.SH "Parameters"
.PP
.RS +3
\fB\fIDevice\fR | all
\fR
.RE
.RS +9
The device name of the file system to be exported. File system
names need not be fully-qualified. \fBfs0\fR is as acceptable as
\fB/dev/fs0\fR. Specify \fBall\fR to export all GPFS file
systems, as well as all disks that do not belong to a file system yet.
This must be the first parameter.
.RE
.PP
.RS +3
\fB-o \fIExportFilesysData\fR
\fR
.RE
.RS +9
The path name of a file to which the file system information is to be
written. This file must be provided as input to the subsequent \fBmmimportfs\fR command.
.RE
.SH "Exit status"
.PP
.PP
.RS +3
\fB0
\fR
.RE
.RS +9
Successful completion.
.RE
.PP
.RS +3
\fBnonzero
\fR
.RE
.RS +9
A failure has occurred.
.RE
.SH "Security"
.PP
You must have root authority to run the \fBmmexportfs\fR command.
.PP
You may issue the \fBmmexportfs\fR command from any node in the GPFS
cluster.
.PP
When using the \fBrcp\fR and \fBrsh\fR commands for remote
communication, a properly configured \fB.rhosts\fR file must exist
in the root user's home directory on each node in the GPFS
cluster. If you have designated the use of a different remote
communication program on either the
\fBmmcrcluster\fR
or
\fBmmchcluster\fR command, you must ensure:
.RS +3
.HP 3
1. Proper authorization is granted to all nodes in the GPFS cluster.
.HP 3
2. The nodes in the GPFS cluster can communicate without the use of a
password, and without any extraneous messages.
.RE
.SH "Examples"
.PP
To export all file systems in the current cluster, issue this
command:
.sp
.nf
mmexportfs all -o /u/admin/exportfile
.fi
.sp
.PP
The output is similar to this:
.sp
.nf
mmexportfs: Processing file system fs1 ...
mmexportfs: Processing file system fs2 ...
mmexportfs: Processing disks that do not belong to any file system ...
mmexportfs: 6027-1371 Propagating the changes to all affected
                      nodes. This is an asynchronous process.
.fi
.sp
.SH "See also"
.PP
mmimportfs Command
.SH "Location"
.PP
\fB/usr/lpp/mmfs/bin\fR
.PP