Virtual TapeServer 6.04.02 for NonStop Servers Release Notes

Known Issues | 9
Known Issues
The following known issues, or “errata,” apply to the 6.04.02 release. The issue tracking
number is provided in parentheses. Refer to this number when making inquiries to Technical
Support.
There is a table of tracking numbers listed in ascending order, with the summary and
document section number, in
Issue Index on page 24.
Hardware and configuration
 Starting a VTD on the NonStop results in two errors logged to debug.log.
Immediately after the NonStop command “SCF START TAPE $VTAPE00” is issued to
start a virtual tape device, one or more of the following messages may appear on the VTS
server in /usr/local/tape/log/debug.log:
Mon Jun 23 14:31:33 2008: [cli_tape 0x05000007] read ERROR on message
rc = 1
These messages are benign and may be ignored. (TL-1802)
 If the controller ID and the host SCSI ID are set to the same value, kernel panics
occur. Kernel panics occur on VTS if two devices set to the same ID. (TL-2303)
WORKAROUND: When using SCSI VTDs, make sure the SCSI controller ID is set to
something different than your host machine's SCSI ID.
 VTS kernel panic may occur after creating VTDs. After creating VTDs, the system
may panic. (TL-2141)
WORKAROUND: Do not configure multiple devices to have the same bus, target, or
LUN values with different initiator values.
 VTD with no connection to a logical tape is still presented on the bus. If a VTD is
created and connected to a logical tape then the VTD is disconnected, the VTD is still
shown to the client. An SG device is created and an Inquiry command succeeds. However,
a Status command does not and the VTD cannot actually be used. (TL-2324)
 ACPI Exception messages are displayed and logged during boot. At boot time,
messages similar to the following may be displayed on the system console and in /var/log/
dmesg. These messages are benign and may be ignored. (TL-2280)
ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device
is not present [20060707]
ACPI: Getting cpuindex for acpiid 0x2
 VTS fails to resume I/O after Fibre Channel cable is disconnected and HBA
times out. If you disconnect the Fibre Channel cable to the VTS for a time period that
exceeds the VTS FC HBA driver timeout value, I/O is interrupted and will not recover.
(TL-1886)
WORKAROUND: Reboot VTS.
 Trace messages may be displayed on the console. These messages can be ignored.
(TL-3032)