User's Manual

hp StorageWorks File System Extender User Guide 231
The HSM file system filter debugging level is always set to 0x0000 after restarting the system
Linux specific
If the HSM file system partition is not listed as noauto in the /etc/fstab file, the HSM file system filter
will be loaded at boot time with the debugging level set to 0x0000 regardless of the settings specified in
the trace.cfg file.
Resolve the problem as follows:
1. Add the following line into the /etc/modules.conf file:
where 0x007f is an example of the specified debug level.
2. Restart FSE for the changes to take effect.
Backup or restore debugging results in job failure
Backup and restore debugging using the -dbg option does not work with the
fsesystem --enable-dbg triggered process debugging.
Make sure you turn on the FSE processes debugging by configuring the trace.cfg file and restarting
FSE.
Contacting support
Gathering information about your problem
You need to gather specific information needed for troubleshooting an FSE implementation. Technical
support needs to know exactly what your problem is and as much information about it as possible. You
should describe if any changes were made to the environment before the problem occurred; include
software version numbers, the nature of the problem (whether the problem occurs intermittently, what errors
are being observed), and a list of third-party vendors.
Checklist for required information
When collecting data about the problem, follow the steps below.
Problem description
Think about the keywords of your problem. Write this down as a one-line description. Specifying what is
the real problem is very important, because technical support will focus on solving that precise problem. If
you describe a wrong problem, you might end up with the original problem still present after the support
have already put significant effort into investigation and solution to another problem.
Log and debug traces of the problem
Reproduce the problem with debugging enabled — for details, see ”Debugging FSE processes” on
page 224. Save the evidence, such as wrong command output or strange error messages, and send it for
lab investigation.Note that without knowing the contents of the fse.log and error.log files, technical
support cannot start investigating the problem.
Reproduction procedure
Write down the procedure for reproducing the problem. This is important for technical support to be able
to investigate and solve the problem.
Workaround discovered?
If you managed to develop your own workaround, describe it and add the description as a part of your
problem report. It might be a useful hint to technical support and other users, or it can lead to an even
better solution.
System information
Linux specific
Use the /opt/fse/sbin/tools/fse_sysinfo.sh script to collect data about the system the FSE
software is running on. The output is shown on stdout, and stored in the file
options hsmfs hsmfs_debug=0x007f