This topic describes where the SAN File System metadata server
logs are stored.
The following logs for the metadata server are stored on the
engine hosting that server.
Table 1. SAN File System metadata server
message log filesLog |
File name |
Location |
Maximum file size |
Audit log |
log.audit |
/usr/tank/server/log |
250 MB |
Dump log |
log.dmp |
/usr/tank/server/log |
– |
Server log |
log.std |
/usr/tank/server/log |
250 MB |
Trace log |
log.trace |
/usr/tank/server/log |
250 MB |
RSA command log |
log.stopengine |
/usr/tank/server/log |
|
Note: - Although the Audit Log (log.audit), Trace Log (log.trace), and Server
Log (log.std) have a maximum file size of 250 MB, SAN File System actually
stores 500 MB of data for each of these logs. When any of these logs reaches
its maximum size, it is renamed to include the extension, .old. If
a file by that name already exists, SAN File System overwrites the existing
file. Then the log is cleared so that it can start accepting new messages
again.
- The log.dmp file starts over for either of these occurrences if the metadata
server has restarted (for example, it restarted due to a server crash):
- The start of each day
- The file reaches a size of 1 MB.
When you display these logs from the master metadata server
using either the administrative command-line interface or the SAN File System
console, you see a consolidated view of all the logs from each engine in the
cluster. The consolidated view of the server message log is called the Cluster
log.
Note: - You can also display the Event Log. This log is actually a subset of the
messages stored in the Cluster Log. It contains only messages with a message
type of event.
Service-only logs
The Dump Log (log.dmp) and the Trace
Log (log.trace) are not used for normal problem determination.
They will not be discussed in detail.