Use this operation to rebalance or restore the replication
factor of all files in a file system.
About this task
This operation runs the following IBM Storage Scale
command:su - gpfsprod -c 'sudo /usr/lpp/mmfs/bin/mmrestripefs <File_System_Name> <Options> -N <Node(s)>
For
more information on this command, see the Related links.
Procedure
- Expand the Administration section
of the GPFS_Manager operations.
- Expand the Restripe File System node.
- In the File System Name field, specify
the name of the file system to be re-striped.
You can determine
the IBM Storage Scale file system name by
running the Get Cluster Status operation.
- In the Options field, click Select to
select one or more of the following options:
- -b
- Rebalances all files across all disks that are not suspended,
even if they are stopped.
- -c
- Scans the file system and compares replicas of metadata and data
for conflicts.
- -m
- Migrates all critical data off suspended disks.
- -p
- Repairs the file placement within the storage pool.
- -r
- Migrates all data off suspended disks.
- -R
- Changes the replication settings of each file, directory, and
system metadata object so that they match the default file system
settings.
For more information on these options, see the Related link.
- In the Node(s) field, specify the
node or list of nodes (separated by semicolons), on which to perform
the operation.
Example:
Node1;Node2;Node3...
You
can specify nodes in a variety of ways. As a best practice, enter
IP addresses (required for IPv6 deployments). For more information,
see the Related link.
You can determine the node names
by running the Get Cluster Status operation.
- Click Submit.
- Click Confirm when asked to validate
your request.
Results
When you run this operation, a new entry is displayed under
the Operation Execution Results list, with
the name Restripe file system. When completed,
the status of the operation changes from Active to Done,
and the Return Value column displays a link
to a log file with the result of the operation. Verify that there
are no errors in this log.