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 |
– |
Failover log |
log.failover |
/usr/tank/server/log |
– |
Server log |
log.std |
/usr/tank/server/log |
250 MB |
Trace log |
log.trace |
/usr/tank/server/log |
250 MB |
Note: - Although log.audit, and log.trace have a maximum file size of 250 MB,
the SAN File System actually stores 500 MB of data for each of these logs.
When either of these logs reaches its maximum size, it is renamed to include
the .old extension. If a file by that name already exists, the existing file
is overwritten. 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:
- 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 actually see a consolidated view of all of the logs from each
engine in the cluster.
Note: - The consolidated view of the server message log is called the cluster
log.
- You can also display the event log. This log is actually a subset of the
messages stored in the cluster log. It contains only those messages that have
a message type of event.
Service only logs
The log.dmp, log.failover, and log.trace
are not used for normal problem determination. They will not be discussed
in detail.