Virtual TapeServer 8.0 Release Notes

Known Issues | 35
 Too many values displayed when an error occurs with a LUN during VTD
creation. When creating a VTD and an error occurs with an existing LUN, the array of
possible values that is displayed can be very large. Instead, the first five possible values
should be presented. (TL-3117)
 VTD names and serial numbers should not be case-sensitive. When creating VTDs,
the web interface checks the case of the specified VTD name and serial number. However,
VTD names and serial numbers are not case-sensitive on the host server. For example,
you can create VTAPE01 and vtape01 on VTS, but the host server only sees VTAPE01.
(TL-3212)
WORKAROUND: Do not specify VTD names or serial numbers that have the same
combination of letters, no matter the case.
 Cannot edit VTD named “0”. If you create a VTD named “0”, you cannot edit the VTD,
though you can delete it. The following error message is displayed. (TL-3721)
The name 0 is already in use by virtual 0 51314695
 PTLI reservation is unclear and may cause error. If you change a port from physical
to virtual mode, an error is displayed if you attempt to create a virtual device on the port
where that physical drive was connected. The reservation of the PTLI is a feature, but the
reason for it may not be clear and the method to clear it up is not indicated by the error
message. (TL-5946)
WORKAROUND: Delete the PTLI using the Advanced link on the Manage Virtual
Devices page.
 Cannot modify target ID of Fibre Channel VTD on Manage Virtual Devices page.
You cannot modify a Fibre Channel VTD's target ID. (TL-5975)
WORKAROUND: Delete the VTD and re-add it with new target ID.
 Incorrect error message displayed when attempting to create a VTL on a bus
that has more drives than LUNs. When attempting to create a VTL on a bus that has
more drives than LUNs, the error message is incorrect. It states, for example, “Unable to
create VTL with the specified number of drives as bus 4 lun 8 combination is already in
use”. The indicated LUN does not exist and, therefore, cannot be in use. (TL-4466)
 VTL creation may only be done as the first device on a port starting with LUN 0.
If a device already occupies LUN 0 on a port, VTL creation will fail indicating there is
another VTL present even if the device already occupying LUN 0 is a virtual tape drive
and not a VTL. (TL-5948)
 Web interface becomes unresponsive after ATIO2s and abort error messages
after trying to create a VTL. If you create a VTL using an occupied bus and then delete
the device using the bus, VTL creation fails and ATIO2s and aborts messages are logged
in dmesg and /var/log/messages. (TL-4191)
WORKAROUND: Reboot VTS.
 Manage Virtual Devices page does not select available values when creating
VTDs. If you attempt to create a VTD after other VTDs have been created, the Manage
Virtual Devices page does not automatically select available values for the LUN and
target. If you do not change the values, the creation will fail. (TL-3491)
WORKAROUND: Modify the LUNs to unused LUNs, modify the target, and then save.
Then, change the LUNs back to the original LUNs.