6.0 HP X9000 File Serving Software File System User Guide (TA768-96043, October 2011)

ibrix_fs -d -f ifs1,ifs2
If data retention is enabled on the file system, include the -R option in the command. For example:
ibrix_fs -d -R -f ifs2
Deleting segments, volume groups, and physical volumes
When deleting segments, volume groups, or physical volumes, you should be aware of the following:
• A segment cannot be deleted until the file system to which it belongs is deleted.
• A volume group cannot be deleted until all segments that were created on it are deleted.
• A physical volume cannot be deleted until all volume groups created on it are deleted.
If you delete physical volumes but do not remove the physical storage from the network, the volumes
might be rediscovered when you next perform a discovery scan on the cluster.
To delete segments:
ibrix_lv -d -s LVLIST
For example, to delete segments ilv1 and ilv2:
ibrix_lv -d -s ilv1,ilv2
To delete volume groups:
bin/ibrix_vg -d -g VGLIST
For example, to delete volume groups ivg1 and ivg2:
ibrix_vg -d -g ivg1,ivg2
To delete physical volumes:
ibrix_pv -d -p PVLIST [-h HOSTLIST]
For example, to delete physical volumes d1, d2, and d3:
ibrix_pv -d -p d[1-3]
Deleting file serving nodes and X9000 clients
Before deleting a file serving node, unmount all file systems from it and migrate any segments that
it owns to a different server. Ensure that the file serving node is not serving as a failover standby
and is not involved in network interface monitoring. To delete a file serving node, use the following
command:
ibrix_server -d -h HOSTLIST
For example, to delete file serving nodes s1.hp.com and s2.hp.com:
ibrix_server -d -h s1.hp.com,s2.hp.com
To delete X9000 clients, use the following command:
ibrix_client -d -h HOSTLIST
Checking and repairing file systems
CAUTION: Do not run ibrix_fsck in corrective mode without the direct guidance of HP Support.
If run improperly, the command can cause data loss and file system damage.
CAUTION: Do not run e2fsck (or any other off-the-shelf fsck program) on any part of a file
system. Doing this can damage the file system.
The ibrix_fsck command can detect and repair file system inconsistencies, which are a symptom
of file system corruption. File system inconsistencies can occur for many reasons, including hardware
failure, power failure, switching off the system without proper shutdown, and failed migration.
40 Maintaining file systems