Troubleshooting the space management client
Use the following information to resolve some typical problems with the space management client.
- Checking the time stamp of a daemon process-ID file
Determine whether a daemon process-ID (PID) file contains a current time stamp. An old time stamp indicates that the daemon stalled. - Creating a dump file
You can create a dump file without stopping the dsmwatchd daemon process. - HSM entries in the syslog file
The HSM client creates entries in the syslog file. The HSM entries in the syslog file and the dsmerror.log file can identify HSM problems. - Client trace classes for the space management client
The space management client provides individual and aggregate trace classes. You can use aggregate trace classes for a shortcut to enable many related trace classes by specifying the aggregate trace class name. - Enabling a Space Management client trace
You can trace the space management client by adding trace options to the dsm.opt client options file. - Enabling daemon traces
You can stop and start trace on HSM daemons. - Log files to aid troubleshooting
When troubleshooting the space management client, you can configure the logs that record HSM activity and error messages. - Commands for displaying HSM information
space management client commands are provided to display HSM statistics and configuration information. - Commands for displaying GPFS information
General Parallel File System (GPFS™) commands are provided to display General Parallel File System (GPFS) information. - Commands for displaying operating system information
Operating system commands are provided to display operating system information. - Other tools for collecting information
A guide to collecting information is available from IBMSoftware Support. - HSM common problems and solutions
space management client common problems are listed. Typical solutions are suggested.