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.

mmrestripefs Comm<strong>and</strong><br />

Assuming that you have enough nodes to saturate the disk servers, <strong>and</strong> have to move all of the data, the<br />

time to read <strong>and</strong> write every block of data is roughly:<br />

2 * fileSystemSize / averageDiskserverDataRate<br />

As an upper bound, due to overhead of scanning all of the metadata, this time should be doubled. If other<br />

jobs are heavily loading the virtual shared disk servers, this time may increase even more.<br />

Note: There is no particular reason to stop all other jobs while the mmrestripefs comm<strong>and</strong> is running.<br />

The CPU load of the comm<strong>and</strong> is minimal on each node <strong>and</strong> only the files that are being restriped<br />

at any moment are locked to maintain data integrity.<br />

Parameters<br />

Device<br />

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

fs0 is as acceptable as /dev/fs0.<br />

This must be the first parameter.<br />

-N {Node[,Node...] | NodeFile | NodeClass}<br />

Specify the nodes that participate in the restripe of the file system. This comm<strong>and</strong> supports all<br />

defined node classes. The default is all (all nodes in the <strong>GPFS</strong> cluster will participate in the<br />

restripe of the file system).<br />

Options<br />

For general information on how to specify node names, see “Specifying nodes as input to <strong>GPFS</strong><br />

comm<strong>and</strong>s” on page 4.<br />

-b Rebalances all files across all disks that are not suspended, even if they are stopped. Although<br />

blocks are allocated on a stopped disk, they are not written to a stopped disk, nor are reads<br />

allowed from a stopped disk, until that disk is started <strong>and</strong> replicated data is copied onto it. The<br />

mmrestripefs comm<strong>and</strong> rebalances <strong>and</strong> restripes the file system. Use this option to rebalance the<br />

file system after adding, changing, or deleting disks in a file system.<br />

Note: Rebalancing of files is an I/O intensive <strong>and</strong> time consuming operation, <strong>and</strong> is important only<br />

for file systems with large files that are mostly invariant. In many cases, normal file update<br />

<strong>and</strong> creation will rebalance your file system over time, without the cost of the rebalancing.<br />

-m Migrates all critical data off any suspended disk in this file system. Critical data is all data that<br />

would be lost if currently suspended disks were removed.<br />

-P PoolName<br />

Directs mmrestripefs to repair only files assigned to the specified storage pool.<br />

-p Directs mmrestripefs to repair the file placement within the storage pool.<br />

Files assigned to one storage pool, but with data in a different pool, will have their data migrated<br />

to the correct pool. Such files are referred to as ill-placed. Utilities, such as the mmchattr<br />

comm<strong>and</strong>, may change a file’s storage pool assignment, but not move the data. The<br />

mmrestripefs comm<strong>and</strong> may then be invoked to migrate all of the data at once, rather than<br />

migrating each file individually. Note that the rebalance operation, specified by the -b option, also<br />

performs data placement on all files, whereas the placement option, specified by -p, rebalances<br />

only the files that it moves.<br />

-r Migrates all data off suspended disks. It also restores all replicated files in the file system to their<br />

designated degree of replication when a previous disk failure or removal of a disk has made some<br />

replica data inaccessible. Use this parameter either immediately after a disk failure to protect<br />

replicated data against a subsequent failure, or before taking a disk offline for maintenance to<br />

protect replicated data against failure of another disk during the maintenance process.<br />

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