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.

Deleting disks from a file system<br />

Before deleting a disk use the mmdf comm<strong>and</strong> to determine whether there is enough free space on the<br />

remaining disks to store the file system. See “Querying file system space” on page 21. Consider how<br />

fragmentation may increase your storage requirements, especially when the file system contains a large<br />

number of small files. A margin of 150 percent of the size of the disks being deleted should be sufficient to<br />

allow for fragmentation when small files predominate. For example, in order to delete a 4 GB disk from<br />

your file system, which contains user home directories with small files, you should first determine that the<br />

other disks in the file system contain a total of 6 GB of free space.<br />

If you do not replicate your file system data, you should rebalance the file system using the mmrestripefs<br />

-b comm<strong>and</strong>. If you replicate your file system data, run the mmrestripefs -r comm<strong>and</strong> after the disk has<br />

been deleted. This ensures that all data will still exist with correct replication after the disk is deleted. The<br />

mmdeldisk comm<strong>and</strong> only migrates data that would otherwise be lost, not data that will be left in a single<br />

copy.<br />

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

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

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

Do not delete stopped disks, if at all possible. Start any stopped disk before attempting to delete it from<br />

the file system. If the disk cannot be started you will have to consider it permanently damaged. You will<br />

need to delete the disk using the appropriate options. If metadata was stored on the disk, you will need to<br />

execute the offline version of the mmfsck comm<strong>and</strong>. See the General Parallel File System: Problem<br />

Determination Guide <strong>and</strong> search for NSD failures for further information on h<strong>and</strong>ling this.<br />

When deleting disks from a file system, the disks may or may not be available. If the disks being deleted<br />

are still available, <strong>GPFS</strong> moves all of the data from those disks to the disks remaining in the file system.<br />

However, if the disks being deleted are damaged, either partially or permanently, it is not possible to move<br />

all of the data <strong>and</strong> you will receive I/O errors during the deletion process. For instructions on how to<br />

h<strong>and</strong>le damaged disks, see the General Parallel File System: Problem Determination Guide <strong>and</strong> search for<br />

Disk media failure.<br />

Specify the file system <strong>and</strong> the names of one or more disks to delete with the mmdeldisk comm<strong>and</strong>. For<br />

example, to delete the disk hd2n97 from the file system fs1 enter:<br />

mmdeldisk fs2 hd2n97<br />

The system displays information similar to:<br />

Deleting disks ...<br />

Scanning ’system’ storage pool<br />

Scanning file system metadata, phase 1 ...<br />

11 % complete on Fri Feb 3 16:01:36 2006<br />

31 % complete on Fri Feb 3 16:01:42 2006<br />

86 % complete on Fri Feb 3 16:01:58 2006<br />

100 % complete on Fri Feb 3 16:02:01 2006<br />

Scan completed successfully.<br />

Scanning file system metadata, phase 2 ...<br />

40 % complete on Fri Feb 3 16:02:04 2006<br />

100 % complete on Fri Feb 3 16:02:08 2006<br />

Scan completed successfully.<br />

Scanning file system metadata, phase 3 ...<br />

9 % complete on Fri Feb 3 16:02:11 2006<br />

42 % complete on Fri Feb 3 16:02:18 2006<br />

100 % complete on Fri Feb 3 16:02:22 2006<br />

Scan completed successfully.<br />

Scanning file system metadata, phase 4 ...<br />

Scan completed successfully.<br />

Scanning user file metadata ...<br />

1 % complete on Fri Feb 3 16:02:32 2006<br />

Chapter 4. Managing disks 29

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!