Troubleshooting

This chapter provides information about troubleshooting the File System Manager software. It contains the following sections:

• Using SAMreports
• Incompatible Software Release
• One Device Displayed Multiple Times
• Inaccessible Server
• No Remaining Space for a VSN
• Damaged or Stale Files in a Recovery Point
• Existing Fault Conditions Not Displayed

Using SAMreports

This section provides information about using SAMreports. It contains the following subsections:

• About SAMreports
• Generating SAMreports
• Displaying SAMreports

---

About SAMreports

The Sun StorageTek QFS and Sun StorageTek SAM Explorer feature collects information from a SAM-QFS environment and writes it to file /var/tmp/SAMreport.<hostname>.<SAM/QFS version>.<date>. The information contained in the SAMreport is an important aid to diagnosing complex problems, and it is needed by an engineer in the event of an escalation.

The SAMreport includes the following information:

• Packaging, revision levels, and licensing information
• Configuration files [mcf(4), archiver.cmd(4), recycler.cmd(4), inquiry.conf(4), defaults.conf(4)]
• Log files (sam-log, messages, archiver.log, recycler.log, releaser.log, trace files)
• Memory dump information

If log files are not routinely collected, an important source of diagnostic information is missing from the SAMreport. Ensure that sites implement a comprehensive logging policy as part of their standard system administration procedures.

Generate a SAMreport in the following circumstances:

• Whenever there is a system panic, core dump, crash, hang, or stall
• As close to any system event as possible

---

Generating SAMreports

To generate a SAMreport:

1. From the Servers menu or the Servers page, choose the server for which you want to generate a SAMreport.

2. From the navigation tree, choose System Administration.

The Server Configuration page is displayed.

3. Scroll down to the SAM Explorer section and click Generate Report.

The Run SAM Explorer page is displayed.

4. Select the directory where you want to store the SAMreport and the number of lines from each log file that should be included in the SAMreport.

5. Click Run.

The system generates the SAMreport in the directory you specified. The current date and time are appended to the file name.

---

Displaying SAMreports

To view the contents of a SAMreport:

1. From the Servers menu or the Servers page, choose the server for which you want to view SAMreports.

2. From the navigation tree, choose System Administration.

The Server Configuration page is displayed.

3. Scroll down to the SAM Explorer section and click the path name of the SAMreport that you want to view.

A window is displayed that enables you to view the contents of the selected file. Click the Next and Previous buttons to page through the report, or enter a line number in the Jump To box and click Go to navigate directory to a specific line.

Note: If the SAMreport path name is not an active link, the SAMreport file might be compressed. Browse to the file on the server and uncompress it so that you can view the contents.

Incompatible Software Release

The File System Manager management station can collect or discover data from any server that has the corresponding or prior update of the following packages installed locally:

• SUNWsamfsr and SUNWsamfsu
• SUNWqfsr and SUNWqfsu

For example, the File System Manager release 3.0 software was released at the same time as the Sun StorageTek QFS and Sun StorageTek SAM release 4, update 6, software. Therefore, the File System Manager release 3.0 browser interface can discover data from a server that has either of the following installed locally:

• Release 4, update 5 or update 6, SUNWsamfsr and SUNWsamfsu packages
• Release 4, update 5 or update 6, SUNWqfsr and SUNWqfsu packages

If the server has an older release level of the packages installed, "Not Supported" is displayed in the Release column on the Servers page.

If the server has a newer release level of the packages installed, a Down icon is displayed on the Servers page.

In either of these situations, do the following to obtain compatible release levels:

1. On the management station and on the server, use the pkginfo(1M) -l (the letter ell) command to verify the package release on the system.

2. Depending on the results of the pkginfo(1M) -l command, do the following:

• If the packages on the management station and server are not compatible, upgrade the system that has the older release.
• If the packages on the management station and server are compatible, use the showrev(1M) -p command on both the management station and server to view the patch release levels.


showrev -p /usr/xpg4/bin/grep -E `SUNWsam|SUNWqfs'

For more information about compatible software and patch release levels, see the README document.

One Device Displayed Multiple Times

If a virtual device is exported from a storage box on two different ports, the current server might view this device as two separate devices. If it does, the File System Manager browser interface will display the device two times.

To address this situation, you must install multipathing software on the server and then click Refresh in the browser interface.

Inaccessible Server

If the File System Manager software cannot communicate with a server, a Down icon is displayed next to the server in the browser interface. There are several reasons this might occur:

• The SUNWqfsr and SUNWqfsu packages or the SUNWsamfsr and SUNWsamfsu packages might not be installed on the server or they might be at incompatible release levels. Search for these packages on the server to verify that they are installed. For information about compatible release levels, see Incompatible Software Release.
• The File System Manager daemon (fsmgmtd) might not be running on the server. Do the following:

a. On the server, use the fsmadm(1M) status command to check whether the daemon is running.

b. If it is not, manually restart the daemon by typing the following:

/opt/SUNWsamfs/sbin/fsmadm restart

You can configure the daemon to start automatically by using the fsmadm(1M) config -a command on the server.

• The rpcbind process might not be running on the server. Do the following:

a. Log in to the server as root.

b. Restart the rpcbind process by typing the following:

/usr/sbin/rpcbind &

• The management station might not be able to remotely administer the server. All hosts that are listed in /opt/SUNWsamfs/sbin/fsmadm on the server can remotely administer the server. To add the management station to the list, log in to the server as root and use the fsmadm(1M) add management-station-name.domain-name command.
• The server is unavailable, it is not connected to the network, or the network itself is unavailable. Check the server's cabling and investigate any possible networking issues.

No Remaining Space for a VSN

If you receive a notification that there is no space available for archiving on a volume (VSN), do one of the following:

• Add more VSNs to the copies of the appropriate archive policy. The appropriate archive policy is the policy that is applied to the files being archived to that VSN. For information about how to perform this procedure, see Modifying VSN Assignments in a Policy Copy.
• Recycle the expired archive copies on the VSN by running the recycler. For more information, see Running Recycling.

Note: You can use the Monitoring Console to track VSN usage. One of the available reports lists archive copies with the highest usage. For more information, see Using the Monitoring Console.

Damaged or Stale Files in a Recovery Point

If you encounter either of the following situations, you must archive the specified files and then create another recovery point of the archiving file system:

• You review the recovery point log file and you find a message that says a file is damaged and cannot be restored with the specified recovery point.
• You receive an email notification that a stale files exists and that the file cannot be restored using the specified recovery point.

Existing Fault Conditions Not Displayed

If you are aware that a server is in a fault condition, but there is no indicator of this fault condition in the browser interface, you might need to restart the Solaris sysevent daemon (syseventd) on the server.

The following explanation applies only to servers with version 4, update 5, or earlier versions of the software.

The reason this might occur is that /opt might not be part of the root file system on the server. If this is the case, the Solaris sysevent daemon (syseventd) starts before /opt is available when the server is rebooted. Because /opt is unavailable to the daemon upon rebooting, the daemon cannot find some of the SUNWsamfs binaries that are required for the File System Manager software to report recent fault conditions or to send Recovery Point Interrupted or File System Overflow notifications.

To address this issue, perform the following:

1. After rebooting the server, log in to the server as root.

2. Type the following at the command prompt:

# pkill -HUP syseventd

The Solaris sysevent daemon is restarted. The daemon can now find the required SUNWsamfs binaries.