[Bacula-users] btape test error on (supported) QUANTUM DLT8000

[Marco P. <pol...@gm...>]

Hello bacula-users!


I am having a rather unpleasant experience... I am trying to get bacula
working with a QUANTUM DLT8000 tape drive that, besides being an old drive
model, is a brand-new device, with only some hours of uptime right now (box
was originally opened by me for this specific application).

I searched the list archives and bug database for some light, but it seems
no one has reported such condition with this tape drive.

I load the drive with a used DLT-IV tape, and run btape as described in the
docs. It all goes fine until:

---------------
=== Append files test ===

This test is essential to Bacula.

I'm going to write one record  in file 0,
                   two records in file 1,
             and three records in file 2

btape: btape.c:475 Rewound "DLT8000" (/dev/nst0)
btape: btape.c:1577 Wrote one record of 64412 bytes.
btape: btape.c:1579 Wrote block to device.
btape: btape.c:505 Wrote 1 EOF to "DLT8000" (/dev/nst0)
btape: btape.c:1577 Wrote one record of 64412 bytes.
btape: btape.c:1579 Wrote block to device.
btape: btape.c:1577 Wrote one record of 64412 bytes.
btape: btape.c:1579 Wrote block to device.
btape: btape.c:505 Wrote 1 EOF to "DLT8000" (/dev/nst0)
btape: btape.c:1577 Wrote one record of 64412 bytes.
btape: btape.c:1579 Wrote block to device.
btape: btape.c:1577 Wrote one record of 64412 bytes.
btape: btape.c:1579 Wrote block to device.
btape: btape.c:1577 Wrote one record of 64412 bytes.
btape: btape.c:1579 Wrote block to device.
btape: btape.c:505 Wrote 1 EOF to "DLT8000" (/dev/nst0)
29-Dec 13:59 btape: Fatal Error at btape.c:368 because:
dev open failed: dev.c:432 Unable to open device "DLT8000" (/dev/nst0):
ERR=\
Input/output error


Append test failed. Attempting again.
Setting "Hardware End of Medium = no
    and "Fast Forward Space File = no
and retrying append test.



=== Append files test ===

This test is essential to Bacula.

I'm going to write one record  in file 0,
                   two records in file 1,
             and three records in file 2

29-Dec 13:59 btape: ABORTING due to ERROR in dev.c:723
dev.c:722 Bad call to rewind. Device "DLT8000" (/dev/nst0) not open
29-Dec 13:59 btape: Fatal Error because: Bacula interrupted by signal 11:
Se\
gmentation violation
Kaboom! btape, btape got signal 11 - Segmentation violation. Attempting
trac\
eback.
Kaboom! exepath=/usr/local/src/bacula-2.4.3/src/stored
Calling: /usr/local/src/bacula-2.4.3/src/stored/btraceback
/usr/local/src/ba\
cula-2.4.3/src/stored/btape 28828
Traceback complete, attempting cleanup ...
--------------

And the device goes offline, with the green "Operate Handle" LED on. The
only way to get the drive back into ready mode is to remove and re-insert
the cartige. I don't know if the traceback should be necessary, but as I
didn't receive the email, I will have to check system config to be able to
get it.

It is very hard to find new DLT-IV tapes where I am located, so, I haven't
tried using a new one to see if the problem persists. I do have a spare one
if needed.

Drive is a QUANTUM DLT8000, External operating on a DIFF SCSI connection.
The adaptor shows as

------------
00:09.0 SCSI storage controller: Adaptec AHA-2940U/UW / AHA-39xx / AIC-7895
(rev 04)
------------

and a tapeinfo results in

-------------
livia:/dev# tapeinfo -f /dev/.static/dev/sg0
Product Type: Tape Drive
Vendor ID: 'QUANTUM '
Product ID: 'DLT8000         '
Revision: '0250'
Attached Changer: No
SerialNumber: 'DFF43P5078'
MinBlock:2
MaxBlock:16777214
SCSI ID: 5
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: 0x85
Density Code: 0x41
BlockSize: 0
DataCompEnabled: no
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x10
DeCompType: 0x10
BOP: yes
Block Position: 0
-------------

Operating system is a standard-kernel Debian Etch (4.0) with all the lastest
kernel updates, uname -a:

-------------
Linux livia 2.6.18-6-k7 #1 SMP Mon Oct 13 16:52:47 UTC 2008 i686 GNU/Linux
-------------

This problem occurs with the lastest stable bacula version (2.4..3) and
2.4.0.


Can anyone give me some hope? :)



Thanks!

Marco Poli