Bareos and HP LTO-5 Drive Problems
Marco Langerwisch
We are having serious trouble with the tape-handling.
- Testing the Tape writing with btape --> all fine
- If we take a new, blank tape, label it, and bareos writes straight forward on tape --> no Problems.
- If we remove the Tape from the Drive an put it back in later, bareos mounts the tape correct, but when then writing starts an the tape winds forward, bareos doesn't find the EOD.
Error: Unable to position to end of data on device "HP-Ultrium3000" (/dev/nst0): ERR=dev.c:1216 ioctl MTFSF error on "HP-Ultrium3000" (/dev/nst0). ERR=Input/output error.
- If we mount another, older tape, that worked before, bareos cannot read the VolumeLabel:
Error: dev.c:1216 ioctl MTFSF error on "HP-Ultrium3000" (/dev/nst0). ERR=Input/output error.
Error: label.c:834 Expecting Volume Label, got FI=4292 Stream=ENCRYPTED-FILE len=36307
- We have loaded the scsicrypto SD-Plugins and disabled Encryption on the Drive:
Drive Crypto Enabled = no
What can I do to solve this problems?
Anyone an idea?
Greetings,
Marco
lst_...@kwsoft.de
Zitat von Marco Langerwisch <mos3...@googlemail.com>:
Have you every restored data with this tape drive?
Have you tried a cleaning tape?
What kind of SAS Controller do you use?
It looks like the tape drive have problems reading it's own tape for
whatever reason. If you have a spare drive try the tape with that one.
Also check the tape drive with "tapeinfo" for raising error counters.
Regards
Andreas
Marco Langerwisch
Hi Andreas,
no we have never restored data from the tapes. We are using the tapes only in Copy-Jobs and the tape-labels are only recognized once, so we can't test till now.
We have also tested with LTO4 Tapes, here the drive recognized the label one time after changing tapes. Second time the same Error experienced as with LTO5 tapes.
We have cleaned the drive with a cleaning tape.
I can't see Errors in the tapeinfo Output (SerialNumber cleared):
# tapeinfo -f /dev/nst0
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'Ultrium 5-SCSI '
Revision: 'Z5AD'
Attached Changer API: No
SerialNumber: 'xxxx'
MinBlock: 1
MaxBlock: 16777215
SCSI ID: 1
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: Not Loaded
Density Code: 0x46
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x1
DeCompType: 0x1
BOP: yes
Block Position: 0
Partition 0 Remaining Kbytes: 800226
Partition 0 Size in Kbytes: 800226
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 0
We are using an IBM PCIe SAS HBA for the TapeDrive, i think it's an "IBM 3Gb SAS HBA v2".
Tomorrow I can do an btape test and send the output.
We don't have a SpareDrive for now.
Regards,
Marco
Marco Langerwisch
Hi,
I've made a new test-run wirh btape.
btape means all running fine (output below)....
What can I check or do to clarify the Problem? Any Ideas?
btape Output:
Tape block granularity is 1024 bytes.
btape: butil.c:292-0 Using device: "HP-Ultrium3000" for writing.
btape: btape.c:499-0 open device "HP-Ultrium3000" (/dev/nst0): OK
*test
=== Write, rewind, and re-read test ===
I'm going to write 10000 records and an EOF
then write 10000 records and an EOF, then rewind,
and re-read the data to verify that it is correct.
This is an *essential* feature ...
btape: btape.c:1184-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1200-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1242-0 Rewind OK.
10000 blocks re-read correctly.
Got EOF on tape.
10000 blocks re-read correctly.
=== Test Succeeded. End Write, rewind, and re-read test ===
btape: btape.c:1310-0 Block position test
btape: btape.c:1322-0 Rewind OK.
Reposition to file:block 0:4
Block 5 re-read correctly.
Reposition to file:block 0:200
Block 201 re-read correctly.
Reposition to file:block 0:9999
Block 10000 re-read correctly.
Reposition to file:block 1:0
Block 10001 re-read correctly.
Reposition to file:block 1:600
Block 10601 re-read correctly.
Reposition to file:block 1:9999
Block 20000 re-read correctly.
=== Test Succeeded. End Write, rewind, and re-read test ===
=== Append files test ===
This test is essential to Bareos.
I'm going to write one record in file 0,
two records in file 1,
and three records in file 2
btape: btape.c:601-0 Rewound "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:499-0 open device "HP-Ultrium3000" (/dev/nst0): OK
btape: btape.c:601-0 Rewound "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1454-0 Now moving to end of medium.
btape: btape.c:652-0 Moved to end of medium.
We should be in file 3. I am at file 3. This is correct!
Now the important part, I am going to attempt to append to the tape.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:601-0 Rewound "HP-Ultrium3000" (/dev/nst0)
Done appending, there should be no I/O errors
Doing Bareos scan of blocks:
1 block of 64448 bytes in file 1
End of File mark.
2 blocks of 64448 bytes in file 2
End of File mark.
3 blocks of 64448 bytes in file 3
End of File mark.
1 block of 64448 bytes in file 4
End of File mark.
Total files=4, blocks=7, bytes = 451,136
End scanning the tape.
We should be in file 4. I am at file 4. This is correct!
The above Bareos scan should have output identical to what follows.
Please double check it ...
=== Sample correct output ===
1 block of 64448 bytes in file 1
End of File mark.
2 blocks of 64448 bytes in file 2
End of File mark.
3 blocks of 64448 bytes in file 3
End of File mark.
1 block of 64448 bytes in file 4
End of File mark.
Total files=4, blocks=7, bytes = 451,136
=== End sample correct output ===
If the above scan output is not identical to the
sample output, you MUST correct the problem
or Bareos will not be able to write multiple Jobs to
the tape.
=== Write, backup, and re-read test ===
I'm going to write three records and an EOF
then backup over the EOF and re-read the last record.
Bareos does this after writing the last block on the
tape to verify that the block was written correctly.
This is not an *essential* feature ...
btape: btape.c:601-0 Rewound "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:838-0 Wrote first record of 64412 bytes.
btape: btape.c:849-0 Wrote second record of 64412 bytes.
btape: btape.c:860-0 Wrote third record of 64412 bytes.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:876-0 Backspaced over EOF OK.
btape: btape.c:881-0 Backspace record OK.
btape: btape.c:899-0
Block re-read correct. Test succeeded!
=== End Write, backup, and re-read test ===
=== Forward space files test ===
This test is essential to Bareos.
I'm going to write five files then test forward spacing
btape: btape.c:601-0 Rewound "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1941-0 Wrote one record of 64412 bytes.
btape: btape.c:1943-0 Wrote block to device.
btape: btape.c:631-0 Wrote 1 EOF to "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:601-0 Rewound "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1668-0 Now forward spacing 1 file.
We should be in file 1. I am at file 1. This is correct!
btape: btape.c:1680-0 Now forward spacing 2 files.
We should be in file 3. I am at file 3. This is correct!
btape: btape.c:601-0 Rewound "HP-Ultrium3000" (/dev/nst0)
btape: btape.c:1693-0 Now forward spacing 4 files.
We should be in file 4. I am at file 4. This is correct!
btape: btape.c:1711-0 Now forward spacing 1 more file.
We should be in file 5. I am at file 5. This is correct!
=== End Forward space files test ===
Marco Langerwisch
Has no one any idea or seen this problem?
Greetings,
Marco
lst_...@kwsoft.de
to my knowledge a "MTFSF error" is a hardware or device error, so
nothing Bareos can do about. What you could try is to switch the tape
device, the controller to some other brand and check the cabeling. We
once had a problem where load/reload tapes lead to a stuck library and
replacing the scsi controller fixed it :-(
For the controller some LSI should be your best choice i guess.
Regards
Andreas