Virtual TapeServer 8.4 Release Notes

Resolved Issues and Enhancements | 12
Resolved Issues and Enhancements
The following changes have been incorporated into the software since the 8.3 release.
Hardware, configuration, and hardware replacement
 In some instances, an IP Address could not be added to eth1 using the netconfig
command. When the netconfig command was used to add the IP Address, “ip_addr
undetermined” was returned. This issue has been resolved. (TL-8206)
 The netconfig command would not continue if a hardware error occurred on a
disconnected port. This issue is no longer seen in version 8.4. (TL-7117)
 If the bus and LUN of a SCSI VTD was changed while the host was scanning
devices, the system may have panicked and the web interface may have stopped
responding. This is no longer an issue in version 8.4. (TL-4018)
General operations
 In 8.3, the appliance may have stopped identifying a 519x tape correctly after a
reboot. This issue has been resolved. (TL-8454, EAR-11143)
 Cartridges might have remained in a locked state after being erased which
resulted in the process failing. This issue has been resolved.(TL-8365, EAR-10543,
EAR-11013, EAR-11287)
 Failures may have occurred if an autoloading pool contained an invalid
cartridge. Invalid cartridges include user created files which are not valid virtual
cartridges and temporary files which may be in the pool when the autoloading function
begins. This issue has been resolved. (TL-3125)
Web interface
This section has been subdivided to better classify the issues.
General
 When deleting a large number of cartridges using FireFox, the popup window
may have appeared wider than the browser window making it impossible to
select the buttons. This issue has been resolved. (TL-7453)
System Status page
 If a file located on the root of the system contained the text “VAULT” followed
by a number, the System Status page may have listed unknown vaults. This issue
has been resolved. (TL-8460, EAR-11121)
 The size of the cluster vaults reported in the systems web interface was rounded
down to the nearest whole number. The size of the cluster vaults will now be reported
with two decimal places for sizes in the GB and TB range and one decimal place for the
KB and MB range. (TL-8449, EAR-11120, EAR-11122)
 The System Status page displayed the names of all the cluster vaults as
VAULT00. The System Status page now will display the correct name for each of the
cluster vaults. (TL-8349, EAR-10390, EAR-10813)