IBM TS2340 User Guide - Page 179

Solaris Device Driver (IBMtape) Reservation Conflict Logging When the device driver receives a reservation conflict during open or after the device has been opened it will log a reservation conflict in the Solaris system log of /var/adm/messages. Prior to logging the error the device driver will issue a Persistent Reserve In command to determine if a SCSI Persistent Reservation is active on the reserving host to get the reserving host initiator WWPN (World Wide Port Name) and reserve key. If successful, the device driver will log this information in the detail data below. After initially logging the reserving host WWPN, subsequent reservation conflicts from the same reserving host WWPN and reservation key will not be logged to prevent multiple entries in the system log until either the reserving host WWPN or reservation key is different than the one initially logged or the device driver has reserved the device and then another reservation conflict occurs. Here are the log examples: 1. The information is logged when the drive is reserved with a Persistent Reservation. log_reserve: Reserving host key 46E48C49413E6EB1 WWPN 210000E08B118BB1 2. The information is logged when the drive is reserved with a SCSI-2 Reserve. log_reserve: Reservation Conflict: read full status failure (rc 16) 3. The information is logged when the drive is reserved but the host reservation information isn't available. log_reserve: Reservation Conflict: No reserving host information is available. Chapter 6. Solaris Tape and Medium Changer Device Driver 161