source: gpfs_3.1_ker2.6.20/share/man/man8/mmrestripefile.8 @ 195

.TH mmrestripefile 02/16/06
mmrestripefile Command
.SH "Name"
.PP
\fBmmrestripefile\fR - Performs a repair operation over the specified list
of files.
.SH "Synopsis"
.PP
\fBmmrestripefile\fR {\fB-m\fR | \fB-r\fR | \fB-b\fR |
\fB-p\fR} {[\fB-F\fR \fIFilenameFile\fR] | \fIFilename\fR
[\fIFilename\fR...]}
.SH "Description"
.PP
The \fBmmrestripefile\fR command performs a repair operation over the
specified list of files. The \fB-F\fR flag allows the user to
specify a file containing the list of file names to be restriped, with one
file name per line.
.PP
The \fBmmrestripefile\fR command attempts to restore the metadata or
data replication factor of the file.
.PP
You must specify one of the four options (\fB-b\fR, \fB-m\fR,
\fB-p\fR, or \fB-r\fR) to indicate how much file data to move.
.PP
If you do not use replication, the \fB-m\fR and \fB-r\fR options are
equivalent. Their behavior differs only on replicated files.
After a successful replicate (\fB-r\fR option), all suspended disks are
empty. A migrate operation, using the \fB-m\fR option, leaves data
on a suspended disk as long as at least one other replica of the data remains
on a disk that is not suspended. Restriping a file system includes
replicating it. The \fB-b\fR option performs all the operations of
the \fB-m\fR and \fB-r\fR options.
.PP
When using SANergy, consider these points:
.RS +3
.HP 3
\(bu If the \fBmmrestripefile\fR command is issued on a file that is locked
by SANergy, the command waits until it is unlocked before proceeding.
.HP 3
\(bu I/O operations from SANergy clients must terminate before using the
\fBmmrestripefile\fR command. If not, the client applications
receive an error.
.RE
.SH "Parameters"
.PP
.RS +3
\fB\fB-F\fR \fIFilenameFile\fR
\fR
.RE
.RS +9
Specifies a file containing a list of names of files to be restriped, one
name per line.
.RE
.PP
.RS +3
\fB\fIFilename\fR
\fR
.RE
.RS +9
Specifies the names of one or more files to be restriped.
.RE
.SH "Options"
.PP
.RS +3
\fB-b
\fR
.RE
.RS +9
Rebalances all files across all disks that are not suspended, even if they
are stopped. Although blocks are allocated on a stopped disk, they are
not written to a stopped disk, nor are reads allowed from a stopped disk,
until that disk is started and replicated data is copied onto it. The
\fBmmrestripefile\fR command rebalances and restripes the file.
.RE
.PP
.RS +3
\fB-m
\fR
.RE
.RS +9
Migrates all critical data off any suspended disk in this file
system. Critical data is all data that would be lost if currently
suspended disks were removed.
.RE
.PP
.RS +3
\fB-p
\fR
.RE
.RS +9
Directs \fBmmrestripefile\fR to repair the file placement within the
storage pool.
.PP
Files assigned to one storage pool, but with data in a different pool, will
have their data migrated to the correct pool. These files are called
ill-placed. Utilities, such as the \fBmmchattr\fR command, may change a file's storage
pool assignment, but not move the data. The \fBmmrestripefile\fR
command may then be invoked to migrate all of the data at once, rather than
migrating each file individually. Note that the rebalance operation,
specified by the \fB-b\fR option, also performs data placement on all
files, whereas the placement option, specified by \fB-p\fR, rebalances only
the files that it moves.
.RE
.PP
.RS +3
\fB-r
\fR
.RE
.RS +9
Migrates all data off suspended disks. It also restores all
replicated files in the file system to their designated degree of replication
when a previous disk failure or removal of a disk has made some replica data
inaccessible. Use this parameter either immediately after a disk
failure to protect replicated data against a subsequent failure, or before
taking a disk offline for maintenance to protect replicated data against
failure of another disk during the maintenance process.
.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 \fBmmrestripefile\fR
command.
.PP
You may issue the \fBmmrestripefile\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 the
\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
This example illustrates restriping a file named \fBtestfile0\fR.
This command confirms that \fBtestfile0\fR is illplaced.
.sp
.nf
mmlsattr -L testfile0
.fi
.sp
.PP
The system displays output similar to:
.sp
.nf
file name:            testfile0
metadata replication: 1 max 2
data replication:     1 max 2
flags:                illplaced
storage pool name:    sp5
fileset name:         root
snapshot name:
.fi
.sp
.PP
To correct the problem, issue this command:
.sp
.nf
mmrestripefile -p testfile0
.fi
.sp
.PP
To confirm the change, issue this command:
.sp
.nf
mmlsattr -L testfile0
.fi
.sp
.PP
The system displays output similar to:
.sp
.nf
file name:            testfile0
metadata replication: 1 max 2
data replication:     1 max 2
flags:
storage pool name:    sp5
fileset name:         root
snapshot name:
.fi
.sp
.SH "See also"
.PP
mmadddisk Command
.PP
mmapplypolicy Command
.PP
mmchattr Command
.PP
mmchdisk Command
.PP
mmdeldisk Command
.PP
mmrpldisk Command
.PP
mmrestripefs Command
.PP
.SH "Location"
.PP
\fB/usr/lpp/mmfs/bin\fR
.PP