VERITAS Volume Manager 4.1 Troubleshooting Guide

Logging Commands and Transactions
Logging Transactions
Chapter 456
NOTE The .translog file is a binary and should not be edited.
The size of the transaction log is checked after an entry has been written so the actual size
may be slightly larger than that specified. When the log reaches a maximum size, the current
transaction log file, translog, is renamed as the next available historic log file,
translog.number, where number is an integer from 1 up to the maximum number of historic
log files that is currently defined, and a new current log file is created.
A limited number of historic log files is preserved to avoid filling up the file system. If the
maximum number of historic log files has been reached, the oldest historic log file is removed,
and the current log file is renamed as that file.
Each log file contains a header that records the host name, host ID, and the date and time
that the log was created.
The following are sample entries from a transaction log file:
Fri Oct 17 13:23:30 2003
Clid = 23460, PID = 21240, Part = 0, Status = 0, Abort Reason = 0
DA_GET Disk_0
DISK_GET_ATTRS Disk_0
DISK_DISK_OP Disk_0 8
DEVNO_GET Disk_0
DANAME_GET 0x160045 0x160072
GET_ARRAYNAME Disk DISKS
CTLR_PTOLNAME 11-08-01
GET_ARRAYNAME Disk DISKS
CTLR_PTOLNAME 21-08-01
DROPPED <no request data>
The first line of each log entry is the time stamp of the transaction. The Clid field corresponds
to the client ID for the connection that the command opened to vxconfigd. The PID field
shows the process ID of the utility that is requesting the operation. The Status and Abort
Reason fields contain error codes if the transaction does not complete normally. The
remainder of the record shows the data that was used in processing the transaction.