Troubleshooting the Configuration Files
After the software packages have been installed, you need to tailor the configuration files to the site installation in order to bring the system into an operational state. Syntactical and typographical errors in these configuration files manifest themselves in unexpected behavior.
|Configuration File Purpose||Default Location|
|Master configuration file||/etc/opt/SUNWsamfs/mcf|
|st device file||/kernel/drv/st.conf|
|samst(7) device file||/kernel/drv/samst.conf|
|Default settings file||/etc/opt/SUNWsamfs/defaults.conf|
The mcf file defines the file system devices and device family sets.
The mcf file is read when sam-fsd(1M) is started. It can be changed at any time, even while sam-fsd is running, but sam-fsd(1M) recognizes mcf file changes only when the daemon is restarted. The following example shows an mcf file for an archiving environment.
The most common problems with the mcf file are syntactical and typographical errors. The sam-fsd(1M) command is a useful tool in debugging the mcf file. If sam-fsd encounters an error as it processes the mcf file, it writes error messages to the SAM-QFS log file (if configured). It also reports errors detected in the following other files, if present:
Enable the changes to the mcf file for a running system by running the samd(1M) command with its config option (as shown at the end of the example above) or by sending the SIGHUP signal to sam-fsd. The procedure for reinitializing sam-fsd to make it recognize mcf file modifications varies, depending on the nature of the changes implemented in the mcf file. For the procedures to be followed in specific circumstances, see the Sun QFS File System Configuration and Administration Guide on OTN.
For direct attached libraries with more than a single drive, the order in which drive entries appear in the mcf file must match the order in which they are identified by the library controller. The drive that the library controller identifies as the first drive must be the first drive entry for that library in the mcf file, and so on.Network attached libraries use different procedures from direct attached libraries, because the drive order for a network attached library is defined by the library control software. For example, for a network attached StorageTek library, the drive mapping in the ACSLS parameters file must match the drives as presented by the ACSLS interface. In this case, the procedure is similar to that for a library without a front panel, except that an additional check is necessary to ensure that the ACSLS parameters file mapping is correct.
Some tape devices that are compatible with SAM-QFS software are not supported by default in the Solaris OS kernel. The file /kernel/drv/st.conf is the Solaris st(7D) tape driver configuration file for all supported tape drives. This file can be modified to enable operation of normally unsupported drives with a SAM-QFS system. Attempting to use any such device in the SAM-QFS environment without updating the st.conf file, or with an incorrectly modified file, causes the system to write messages such as the following to the device log file:
If your configuration is to include devices not supported by the Solaris OS, consult the /opt/SUNWsamfs/examples/st.conf_changes file for instructions on how to modify the st.conf file.For example, the IBM LTO drive is not supported by default in Solaris kernel. The following example shows the lines you need to add to the st.conf file in order to include IBM LTO drives in a SAM-QFS environment.
The st.conf file is read only when the st driver is loaded, so if the /kernel/drv/st.conf file is modified, perform one of the following actions in order to direct the system to recognize the changes:
- Use the unload(1M) and modload(1M) command to reload the driver.
- Reboot the system.