Virtual TapeServer 6.04.03 for NonStop Servers Release Notes

Known Issues | 10
Known Issues
The following known issues, or “errata,” apply to the 6.04.03 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 36.
Hardware and configuration
 No automatic reboot after setting system limits on Fibre Channel ports. If you
use the Manage System Limits page to configure the Fibre Channel ports, a message is
displayed and broadcast that a reboot will occur though it does not. You must reboot after
setting system limits. (TL-4000)
 Exports to SCSI physical drives may fail. When simultaneously running backups to a
VTD and writing to external SCSI storage device, various errors can occur that cause the
loss of use of the SCSI storage device. Exports may fail with an RC9 return code. This is
due to a problem with the VTS version of the Adaptec AIC driver used for writing to SCSI
targets. The driver needs to be updated to be compliant with the Linux 2.6 kernel. (TL-
3924, EAR 5702, EAR 5744)
 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 are 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.
 Kernel panic may occur if SCSI VTD is edited while host is scanning devices. If
you change the bus and LUN of a SCSI VTD and the host is scanning devices, the system
may panic and the web interface may stop responding. (TL-4018)
 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.
 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
 Trace messages may be displayed on the console. These messages can be ignored.
(TL-3032)