HP StorageWorks Scalable File Share - Manual (Page 245)

Troubleshooting file systems 9–21
9.26 Troubleshooting file systems
This section provides information for troubleshooting problems with file systems, and is organized as follows:
• Problems creating a file system (Section 9.26.1)
• Identifying servers serving OST services (Section 9.26.2)
• The start filesystem command may fail twice (Section 9.26.3)
• Troubleshooting the stop filesystem command (Section 9.26.4)
• Using the MPI Lustre repair utility to repair file systems (Section 9.26.5)
• MDS or OST services stay in the recovering state (Section 9.26.6)
• MDS and OST service recovery process (Section 9.26.7)
• Rebalancing file system services (Section 9.26.8)
• Troubleshooting supplementary groups access (Section 9.26.9)
9.26.1 Problems creating a file system
If you have previously deleted a file system, you may encounter problems when you try to create a new file
system; for example, output similar to the following may be displayed:
Would you like to create this filesystem? []: yes
Filesystem being created
Command id 139
10:52:08 south2 -- 10:52:15 south2 -- Command Failed on: south2
10:52:15 south2 -- Adding newfs filesystem to database
10:52:15 south2 -- Adding OSTS for newfs filesystem to database
10:52:15 south2 -- Failed configure: Failed to stop MDS raid:
10:52:15 south2 -- lsRaidLovGroupStopRaid: lsRaidStopRaid: /dev/md0: Device or
resource busy
This is because the
delete filesystem
command may not have completely removed all of the
information for the file system that was deleted.
Section 5.5 provides information on recovering from a failure of the
create filesystem
command.
Follow the instructions in that section to attempt to complete the creation of the file system.
If the creation of the new file system continues to fail, delete the old file system information, as shown in the
following example:
1. Unmount the file system by entering the command shown in the following example on each client
node that has mounted the file system:
# sfsumount oldfs
where
oldfs
is the name of the file system to be unmounted.
NOTE: If some of the MDS or OST services have already stopped or been deleted in the HP SFS
system, the
sfsumount
(8) command may not succeed in unloading the software on a client
node. In this situation, you may need to reboot the client node.
2. Delete the file system by entering the command shown in the following example, where
oldfs
is the
file system to be deleted:
# sfsmgr
.
.
.
sfs> delete filesystem oldfs