Virtual TapeServer 6.04.03.01 for NonStop Servers Release Notes

Resolved Issues and Enhancements | 5
Resolved Issues and Enhancements
The following changes have been incorporated into the software since the 6.04.03 release.
Hardware and configuration
 Exports to SCSI physical drives may have failed. When simultaneously running
backups to a VTD and writing to external SCSI storage device, various errors could occur
that caused the loss of use of the SCSI storage device. Exports may have failed with an
RC9 return code. This was due to a problem with the VTS version of the Adaptec AIC
driver used for writing to SCSI targets. Now, you can disable the VTS target mode driver
on the Manage Systems Limits page. Doing so will use the native Linux SCSI driver,
which will perform much faster. This option is only available if you do not have SCSI
VTDs.(TL-3924, EAR 5702, EAR 5744)
General operations
 vtsa user could not issue mount command. From the command line, the vtsa user
could not issue the /bin/mount command. This has been fixed. (TL-3981)
 SCSI commands timed out for MODE_SELECT, TUR, and WRITE_FILEMARKS.
VTS flushed its cache causing delayed responses to the SCSI commands sent by the host
server. The amount of memory used for disk write caching has now been tuned and this
problem no longer occurs. (TL-4207, EAR 6223)
 Physical devices now automatically created when connected. A new device type is
now listed on the Manage Connections page when physical device is connected to VTS.
“auto-” precedes the name of new device emulation to indicate that it was automatically
created when the new physical device was attached. (TL-3797)
 Check condition now returned for non-existent or unsupported pages. A mode
sense command for a page that does not exist or is not supported by the device emulation
now returns a check condition. Previously, VTS was returning all pages supported,
causing the host to be confused and interpret the emulation as something other than the
device type. (TL-3820, TL-3657)
 SCSI performance was 80MB/sec rather than 160MB/sec. Previously, the initiator
was not performing SCSI parallel protocol request (PPR) negotiations as required for
U160+ speeds. This was because the INQUIRY response from VTDs was not setting the
SPI3 bit to allow double-transition (DT) and single transition (ST) clocking. These bits are
necessary to support U160+ speeds. This has been fixed. (TL-4105)
 Error logged to /var/log/httpd/error_log when a cartridge was mounted. When
mounting a cartridge, an error similar to the following was logged in /var/log/httpd/
error_log:
vtmeta: Error /VAULT00/POOL1/CART1: Unable to lock file.
This was a logging issue only and no longer occurs. (TL-2453)