Virtual TapeServer 6.04.02 for NonStop Servers Release Notes

Known Issues | 10
General operations
 Duplicate cartridges are imported. It is possible to import duplicate cartridges by
importing a pool of cartridges into a different pool; this was also true in earlier releases.
(TL-3169)
WORKAROUND: To prevent this problem, import a pool of cartridges into the same pool
from which the cartridges were originally exported. To fix this problem if it occurs, delete
the cartridges from the new pool and then re-import to the original pool.
 Operations fail and errors are logged when log files exceed 2GB in size. When a
log file grows to over 2GB in size in less than a day, some commands will fail and errors
similar to the following are logged. (TL-3139)
ERROR: C06001 is locked by Filesize limit exceeded.
WORKAROUND: Remove the log file or wait until VTS rotates the file at 4AM.
 traceInit messages are logged to /var/log/messages. Messages similar to the
following are logged to /var/log/messages. These messages can be ignored. (TL-3151)
Jun 2 13:20:54 VTS06 slave: traceInit: Opening /proc/crds-trace
failed, No such file or directory
 Tape can be mounted in deleted VTD. If you delete a VTD, VTS still allows you to
mount a virtual tape in the deleted VTD. No data is lost but the tape is locked. (TL-3156)
 Date and time shown for locked cartridges is incorrect. The timestamp used for the
date and time when a cartridge is locked is incorrect. (TL-2551)
 Error logged to /var/log/httpd/error_log when a cartridge is mounted. When
mounting a cartridge, an error similar to the following is logged in /var/log/httpd/
error_log:
vtmeta: Error /VAULT00/POOL1/CART1: Unable to lock file.
This is a logging issue only; the message can be ignored. (TL-2453)
 Failures may occur if an autoloading pool contains an invalid cartridge. Only
valid cartridges should be added to pools within vaults. If other files are there,
inconsistent or unpredictable behavior may occur. (TL-3125)
WORKAROUND: Restart the Tapeserver service.
 New VTDs not recognized until VTS is rebooted. After you create a VTD, you must
reboot VTS. Otherwise, VTS does not “see” the device. (TL-2719)
 SNMPD error messages are generated during installation. After installation, the
following messages are in /var/log/snmpd.log. (TL-2289, TL-2288)
Oct 27 12:21:46 localhost snmpd[7983]: c64 32 bit check failed.
Oct 27 12:20:46 localhost snmpd[7983]: cmaX: sent ColdStarts on ports
25376 to 25393
Oct 27 12:20:46 localhost snmpd[7983]: error finding row index in
_ifXTable_container_row_restore
 Error message written to debug log if a physical tape drive is added that is
similar to an existing one. If an Ultrium physical tape drive is attached to VTS and one
is already in the database, an error message may appear in the debug log indicating that
it was unable to add this physical tape to the database. This message can be ignored. (TL-
2290)