Discussion:
[Bacula-users] A *different* append test problem with btape
Steve Garcia
2017-07-20 19:47:31 UTC
Permalink
I have a *different* problem with a new tape drive and btape, also failing during the append test.

The read/write test passes with no trouble, but the append test not only fails, but it takes the tape drive offline. Once this happens, the drive is not accessible until the tape is physically dismounted and then remounted. Once this happens, the drive comes back to life, but it will go offline again if the append test is re-attempted.

The btape failure message suggested using a fixed block size, but making that change didn't seem to make any difference.

I tried downloading the IBM ITDT utility and running all its tests, but the drive passed with flying colors in the ITDT diagnostics.

I am running bacula 7.4.4 on a new Debian stretch (Debian 9) server with a new tape library and tape drive. The new drive is an IBM ULT3580-HH6 LTO-6 drive in a Dell TL-2000 library. I have an existing bacula instance running on a Debian jesse (debian 8) server, and my plan is to add the new tape library as an additional pool for the existing instance. For now, though, unless I can get the drive to work with bacula, planning how to set bacula itself up doesn't matter.

What steps can I do to troubleshoot this?

One thing I notice is that lsscsi shows the tape drive twice, but there is only one actual drive. Could this be a part of the problem?


***@odin:/etc/bacula/scripts# ./mtx-changer /dev/autochanger1 load 1 /dev/nst0 0
Loading media from Storage Element 1 into drive 0...done


***@odin:/etc/bacula/scripts# ./mtx-changer /dev/autochanger1 listall
D:0:F:1:000015L6
S:1:E
S:2:F:000018L6
S:3:F:000021L6
S:4:F:CLNU00L1
S:5:F:000014L6
S:6:F:000017L6
S:7:F:000020L6
S:8:F:CLN005L3
S:9:F:000013L6
S:10:F:000016L6
S:11:F:000019L6
S:12:F:000012L6
S:13:F:000009L6
S:14:F:000006L6
S:15:F:000003L6
S:16:F:000011L6
S:17:F:000008L6
S:18:F:000005L6
S:19:F:000002L6
S:20:F:000010L6
S:21:F:000007L6
S:22:F:000004L6
S:23:F:000001L6
I:24:E


***@odin:/etc/bacula/scripts# btape -c ../bacula-sd.conf /dev/nst0
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
test
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*

=== 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:1154-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1170-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1212-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:1279-0 Block position test
btape: btape.c:1291-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 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:576-0 Rewound "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/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

btape: btape.c:573-0 Bad status from rewind. ERR=tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: block.c:144-0 Attempt to write on read-only Volume. dev="Drive-1" (/dev/nst0)
13-Jul 16:07 btape JobId 0: Fatal error: block.c:144 Attempt to write on read-only Volume. dev="Drive-1" (/dev/nst0)
btape: btape.c:1906-0 Error writing block to device.
btape: Fatal Error at tape_dev.c:918 because:
tape_dev.c:917 Bad call to weof_dev. Device not open
13-Jul 16:07 btape: Fatal Error at tape_dev.c:918 because:
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to weof_dev. Device not open

btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: btape.c:1906-0 Error writing block to device.
btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: btape.c:1906-0 Error writing block to device.
btape: Fatal Error at tape_dev.c:918 because:
tape_dev.c:917 Bad call to weof_dev. Device not open
13-Jul 16:07 btape: Fatal Error at tape_dev.c:918 because:
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to weof_dev. Device not open

btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: btape.c:1906-0 Error writing block to device.
btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: btape.c:1906-0 Error writing block to device.
btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: btape.c:1906-0 Error writing block to device.
btape: Fatal Error at tape_dev.c:918 because:
tape_dev.c:917 Bad call to weof_dev. Device not open
13-Jul 16:07 btape: Fatal Error at tape_dev.c:918 because:
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to weof_dev. Device not open

btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:07 btape: Fatal Error at btape.c:467 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error



That appears *NOT* to have corrected the problem.

Append test failed.


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Unable to correct the problem. You MUST fix this
problem before Bacula can use your tape drive correctly

Perhaps running Bacula in fixed block mode will work.
Do so by setting:

Minimum Block Size = nnn
Maximum Block Size = nnn

in your Storage daemon's Device definition.
nnn must match your tape driver's block size, which
can be determined by reading your tape manufacturers
information, and the information on your kernel dirver.
Fixed block sizes, however, are not normally an ideal solution.

Some systems, e.g. OpenBSD, require you to set
Use MTIOCGET= no
in your device resource. Use with caution.
*quit


***@odin:/etc/bacula/scripts# btape -c ../bacula-sd.conf /dev/nst0
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
btape: Fatal Error at device.c:300 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

13-Jul 16:10 btape: Fatal Error at device.c:300 because:
dev open failed: tape_dev.c:164 Unable to open device "Drive-1" (/dev/nst0): ERR=Input/output error

btape: butil.c:199-0 Cannot open "Drive-1" (/dev/nst0)
13-Jul 16:10 btape JobId 0: Fatal error: butil.c:199 Cannot open "Drive-1" (/dev/nst0)


***@odin:/etc/bacula/scripts# ./mtx-changer /dev/autochanger1 unload 1 /dev/nst0 0
Unloading drive 0 into Storage Element 1...done

***@odin:/etc/bacula/scripts# ./mtx-changer /dev/autochanger1 load 1 /dev/nst0 0
Loading media from Storage Element 1 into drive 0...done


***@odin:/etc/bacula/scripts# btape -c ../bacula-sd.conf /dev/nst0
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*

***@odin:/etc/bacula/scripts# lsscsi -g
[0:2:0:0] disk DELL PERC H730 Mini 4.27 /dev/sda /dev/sg0
[1:0:0:0] tape IBM ULT3580-HH6 G9P1 /dev/st0 /dev/sg2
[1:0:0:1] mediumx IBM 3573-TL E.30 /dev/sch0 /dev/sg3
[1:0:1:0] tape IBM ULT3580-HH6 G9P1 /dev/st1 /dev/sg4
[1:0:1:1] mediumx IBM 3573-TL E.30 /dev/sch1 /dev/sg5
[6:2:0:0] disk DELL PERC H830 Adp 4.27 /dev/sdb /dev/sg1
[12:0:0:0] cd/dvd PLDS DVD-ROM DS-8DBSH MD52 /dev/sr0 /dev/sg6


***@odin:/etc/bacula/scripts# tapeinfo -f /dev/sg2
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULT3580-HH6 '
Revision: 'G9P1'
Attached Changer API: No
SerialNumber: '10WT110956'
MinBlock: 1
MaxBlock: 8388608
SCSI ID: 0
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: 0x68
Density Code: 0x5a
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0xff
DeCompType: 0xff
BOP: yes
Block Position: 0
Partition 0 Remaining Kbytes: -1
Partition 0 Size in Kbytes: -1
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 3


Device {
Name = Drive-1 #
Description = "LT06 inside Dell TL2000 Library"
Drive Index = 0
Media Type = LT06
Archive Device = /dev/nst0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
SpoolDirectory = "/var/spool/bacula"
MaximumSpoolSize = 485G
Maximum Network Buffer Size = 65536
# MaximumBlockSize = 256k
# MinimumBlockSize = 256k
Offline On Unmount = yes
# #
# # Enable the Alert command only if you have the mtx package loaded
# # Note, apparently on some systems, tapeinfo resets the SCSI controller
# # thus if you turn this on, make sure it does not reset your SCSI
# # controller. I have never had any problems, and smartctl does
# # not seem to cause such problems.
# #
#Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = "sh -c 'smartctl -H -l error %c'"
}


--
Steve Garcia
Ignorance killed the cat, curiosity was framed.
Ana Emília M. Arruda
2017-07-23 02:08:08 UTC
Permalink
Hello Steve,

It seems this is due to "Offline On Unmount = yes". The default for this
directive is no. Usually, it is not necessary to set this directive to "no"
when dealing with tape libraries.

This will cause the tape to be offline after WEOF and not available to be
used for append.

Do you have any special reason to have this directive configured?

Best regards,
Ana
Post by Steve Garcia
I have a *different* problem with a new tape drive and btape, also failing
during the append test.
The read/write test passes with no trouble, but the append test not only
fails, but it takes the tape drive offline. Once this happens, the drive
is not accessible until the tape is physically dismounted and then
remounted. Once this happens, the drive comes back to life, but it will go
offline again if the append test is re-attempted.
The btape failure message suggested using a fixed block size, but making
that change didn't seem to make any difference.
I tried downloading the IBM ITDT utility and running all its tests, but
the drive passed with flying colors in the ITDT diagnostics.
I am running bacula 7.4.4 on a new Debian stretch (Debian 9) server with a
new tape library and tape drive. The new drive is an IBM ULT3580-HH6 LTO-6
drive in a Dell TL-2000 library. I have an existing bacula instance
running on a Debian jesse (debian 8) server, and my plan is to add the new
tape library as an additional pool for the existing instance. For now,
though, unless I can get the drive to work with bacula, planning how to set
bacula itself up doesn't matter.
What steps can I do to troubleshoot this?
One thing I notice is that lsscsi shows the tape drive twice, but there is
only one actual drive. Could this be a part of the problem?
Loading media from Storage Element 1 into drive 0...done
D:0:F:1:000015L6
S:1:E
S:2:F:000018L6
S:3:F:000021L6
S:4:F:CLNU00L1
S:5:F:000014L6
S:6:F:000017L6
S:7:F:000020L6
S:8:F:CLN005L3
S:9:F:000013L6
S:10:F:000016L6
S:11:F:000019L6
S:12:F:000012L6
S:13:F:000009L6
S:14:F:000006L6
S:15:F:000003L6
S:16:F:000011L6
S:17:F:000008L6
S:18:F:000005L6
S:19:F:000002L6
S:20:F:000010L6
S:21:F:000007L6
S:22:F:000004L6
S:23:F:000001L6
I:24:E
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
test
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*
=== 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:1154-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1170-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1212-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:1279-0 Block position test
btape: btape.c:1291-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 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:576-0 Rewound "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/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
btape: btape.c:573-0 Bad status from rewind. ERR=tape_dev.c:164 Unable to
open device "Drive-1" (/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: block.c:144-0 Attempt to write on read-only Volume. dev="Drive-1" (/dev/nst0)
13-Jul 16:07 btape JobId 0: Fatal error: block.c:144 Attempt to write on
read-only Volume. dev="Drive-1" (/dev/nst0)
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
That appears *NOT* to have corrected the problem.
Append test failed.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Unable to correct the problem. You MUST fix this
problem before Bacula can use your tape drive correctly
Perhaps running Bacula in fixed block mode will work.
Minimum Block Size = nnn
Maximum Block Size = nnn
in your Storage daemon's Device definition.
nnn must match your tape driver's block size, which
can be determined by reading your tape manufacturers
information, and the information on your kernel dirver.
Fixed block sizes, however, are not normally an ideal solution.
Some systems, e.g. OpenBSD, require you to set
Use MTIOCGET= no
in your device resource. Use with caution.
*quit
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: butil.c:199-0 Cannot open "Drive-1" (/dev/nst0)
13-Jul 16:10 btape JobId 0: Fatal error: butil.c:199 Cannot open "Drive-1" (/dev/nst0)
Unloading drive 0 into Storage Element 1...done
Loading media from Storage Element 1 into drive 0...done
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*
[0:2:0:0] disk DELL PERC H730 Mini 4.27 /dev/sda /dev/sg0
[1:0:0:0] tape IBM ULT3580-HH6 G9P1 /dev/st0 /dev/sg2
[1:0:0:1] mediumx IBM 3573-TL E.30 /dev/sch0 /dev/sg3
[1:0:1:0] tape IBM ULT3580-HH6 G9P1 /dev/st1 /dev/sg4
[1:0:1:1] mediumx IBM 3573-TL E.30 /dev/sch1 /dev/sg5
[6:2:0:0] disk DELL PERC H830 Adp 4.27 /dev/sdb /dev/sg1
[12:0:0:0] cd/dvd PLDS DVD-ROM DS-8DBSH MD52 /dev/sr0 /dev/sg6
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULT3580-HH6 '
Revision: 'G9P1'
Attached Changer API: No
SerialNumber: '10WT110956'
MinBlock: 1
MaxBlock: 8388608
SCSI ID: 0
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: 0x68
Density Code: 0x5a
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0xff
DeCompType: 0xff
BOP: yes
Block Position: 0
Partition 0 Remaining Kbytes: -1
Partition 0 Size in Kbytes: -1
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 3
Device {
Name = Drive-1 #
Description = "LT06 inside Dell TL2000 Library"
Drive Index = 0
Media Type = LT06
Archive Device = /dev/nst0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
SpoolDirectory = "/var/spool/bacula"
MaximumSpoolSize = 485G
Maximum Network Buffer Size = 65536
# MaximumBlockSize = 256k
# MinimumBlockSize = 256k
Offline On Unmount = yes
# #
# # Enable the Alert command only if you have the mtx package loaded
# # Note, apparently on some systems, tapeinfo resets the SCSI controller
# # thus if you turn this on, make sure it does not reset your SCSI
# # controller. I have never had any problems, and smartctl does
# # not seem to cause such problems.
# #
#Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = "sh -c 'smartctl -H -l error %c'"
}
--
Steve Garcia
Ignorance killed the cat, curiosity was framed.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
https://lists.sourceforge.net/lists/listinfo/bacula-users
Steve Garcia
2017-07-24 19:14:08 UTC
Permalink
Thank you!

This solved my problem. I was starting to worry that we had purchased a fairly expensive drive that wasn't going to work -- tough to explain to my boss.

I had copied my configuration from our older instance of bacula, which is using the same kind of library, but with the LTO3 version of the same model tape drive. I'm not sure why this setting was defined in my older configuration, but I set that up in 2009, so whatever reason I may have had has completely faded. In any case, it's working with the old drive and library, so I probably will leave it alone there. I've gotten rid of it for the new library.

Now I have to figure out a strategy for bringing the new library into the mix. Other messages have let me know that my idea of making both part of the same pool is not a good idea.
Post by Ana Emília M. Arruda
Hello Steve,
It seems this is due to "Offline On Unmount = yes". The default for this
directive is no. Usually, it is not necessary to set this directive to "no"
when dealing with tape libraries.
This will cause the tape to be offline after WEOF and not available to be
used for append.
Do you have any special reason to have this directive configured?
Best regards,
Ana
Post by Steve Garcia
I have a *different* problem with a new tape drive and btape, also failing
during the append test.
The read/write test passes with no trouble, but the append test not only
fails, but it takes the tape drive offline. Once this happens, the drive
is not accessible until the tape is physically dismounted and then
remounted. Once this happens, the drive comes back to life, but it will go
offline again if the append test is re-attempted.
The btape failure message suggested using a fixed block size, but making
that change didn't seem to make any difference.
I tried downloading the IBM ITDT utility and running all its tests, but
the drive passed with flying colors in the ITDT diagnostics.
I am running bacula 7.4.4 on a new Debian stretch (Debian 9) server with a
new tape library and tape drive. The new drive is an IBM ULT3580-HH6 LTO-6
drive in a Dell TL-2000 library. I have an existing bacula instance
running on a Debian jesse (debian 8) server, and my plan is to add the new
tape library as an additional pool for the existing instance. For now,
though, unless I can get the drive to work with bacula, planning how to set
bacula itself up doesn't matter.
What steps can I do to troubleshoot this?
One thing I notice is that lsscsi shows the tape drive twice, but there is
only one actual drive. Could this be a part of the problem?
/dev/nst0 0
Loading media from Storage Element 1 into drive 0...done
D:0:F:1:000015L6
S:1:E
S:2:F:000018L6
S:3:F:000021L6
S:4:F:CLNU00L1
S:5:F:000014L6
S:6:F:000017L6
S:7:F:000020L6
S:8:F:CLN005L3
S:9:F:000013L6
S:10:F:000016L6
S:11:F:000019L6
S:12:F:000012L6
S:13:F:000009L6
S:14:F:000006L6
S:15:F:000003L6
S:16:F:000011L6
S:17:F:000008L6
S:18:F:000005L6
S:19:F:000002L6
S:20:F:000010L6
S:21:F:000007L6
S:22:F:000004L6
S:23:F:000001L6
I:24:E
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
test
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*
=== 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:1154-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1170-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1212-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:1279-0 Block position test
btape: btape.c:1291-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 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:576-0 Rewound "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/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
btape: btape.c:573-0 Bad status from rewind. ERR=tape_dev.c:164 Unable to
open device "Drive-1" (/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: block.c:144-0 Attempt to write on read-only Volume. dev="Drive-1"
(/dev/nst0)
13-Jul 16:07 btape JobId 0: Fatal error: block.c:144 Attempt to write on
read-only Volume. dev="Drive-1" (/dev/nst0)
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call to
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
That appears *NOT* to have corrected the problem.
Append test failed.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Unable to correct the problem. You MUST fix this
problem before Bacula can use your tape drive correctly
Perhaps running Bacula in fixed block mode will work.
Minimum Block Size = nnn
Maximum Block Size = nnn
in your Storage daemon's Device definition.
nnn must match your tape driver's block size, which
can be determined by reading your tape manufacturers
information, and the information on your kernel dirver.
Fixed block sizes, however, are not normally an ideal solution.
Some systems, e.g. OpenBSD, require you to set
Use MTIOCGET= no
in your device resource. Use with caution.
*quit
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: butil.c:199-0 Cannot open "Drive-1" (/dev/nst0)
13-Jul 16:10 btape JobId 0: Fatal error: butil.c:199 Cannot open "Drive-1"
(/dev/nst0)
/dev/nst0 0
Unloading drive 0 into Storage Element 1...done
/dev/nst0 0
Loading media from Storage Element 1 into drive 0...done
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*
[0:2:0:0] disk DELL PERC H730 Mini 4.27 /dev/sda /dev/sg0
[1:0:0:0] tape IBM ULT3580-HH6 G9P1 /dev/st0 /dev/sg2
[1:0:0:1] mediumx IBM 3573-TL E.30 /dev/sch0 /dev/sg3
[1:0:1:0] tape IBM ULT3580-HH6 G9P1 /dev/st1 /dev/sg4
[1:0:1:1] mediumx IBM 3573-TL E.30 /dev/sch1 /dev/sg5
[6:2:0:0] disk DELL PERC H830 Adp 4.27 /dev/sdb /dev/sg1
[12:0:0:0] cd/dvd PLDS DVD-ROM DS-8DBSH MD52 /dev/sr0 /dev/sg6
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULT3580-HH6 '
Revision: 'G9P1'
Attached Changer API: No
SerialNumber: '10WT110956'
MinBlock: 1
MaxBlock: 8388608
SCSI ID: 0
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: 0x68
Density Code: 0x5a
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0xff
DeCompType: 0xff
BOP: yes
Block Position: 0
Partition 0 Remaining Kbytes: -1
Partition 0 Size in Kbytes: -1
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 3
Device {
Name = Drive-1 #
Description = "LT06 inside Dell TL2000 Library"
Drive Index = 0
Media Type = LT06
Archive Device = /dev/nst0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
SpoolDirectory = "/var/spool/bacula"
MaximumSpoolSize = 485G
Maximum Network Buffer Size = 65536
# MaximumBlockSize = 256k
# MinimumBlockSize = 256k
Offline On Unmount = yes
# #
# # Enable the Alert command only if you have the mtx package loaded
# # Note, apparently on some systems, tapeinfo resets the SCSI controller
# # thus if you turn this on, make sure it does not reset your SCSI
# # controller. I have never had any problems, and smartctl does
# # not seem to cause such problems.
# #
#Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = "sh -c 'smartctl -H -l error %c'"
}
--
Steve Garcia
Ignorance killed the cat, curiosity was framed.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
https://lists.sourceforge.net/lists/listinfo/bacula-users
Ana Emília M. Arruda
2017-07-24 20:22:05 UTC
Permalink
Hello Steve,

Great it worked!

You are right, it is not a good idea to have both tape libraries share the
same pool/media type. Mainly because LTO-6 is more than 2 generations ahead
LTO-3. This means your LTO-6 drives will not be able to even read the LTO-3
tapes.

I would recommend you to have a different pool for your new tape library
and redirect the jobs to use the new one, if the old one will not be used
for writing anymore. You may let it there until you have useful data to
restore then.

Best regards,
Ana
Post by Steve Garcia
Thank you!
This solved my problem. I was starting to worry that we had purchased a
fairly expensive drive that wasn't going to work -- tough to explain to my
boss.
I had copied my configuration from our older instance of bacula, which is
using the same kind of library, but with the LTO3 version of the same model
tape drive. I'm not sure why this setting was defined in my older
configuration, but I set that up in 2009, so whatever reason I may have had
has completely faded. In any case, it's working with the old drive and
library, so I probably will leave it alone there. I've gotten rid of it
for the new library.
Now I have to figure out a strategy for bringing the new library into the
mix. Other messages have let me know that my idea of making both part of
the same pool is not a good idea.
Post by Ana Emília M. Arruda
Hello Steve,
It seems this is due to "Offline On Unmount = yes". The default for this
directive is no. Usually, it is not necessary to set this directive to
"no"
Post by Ana Emília M. Arruda
when dealing with tape libraries.
This will cause the tape to be offline after WEOF and not available to be
used for append.
Do you have any special reason to have this directive configured?
Best regards,
Ana
Post by Steve Garcia
I have a *different* problem with a new tape drive and btape, also
failing
Post by Ana Emília M. Arruda
Post by Steve Garcia
during the append test.
The read/write test passes with no trouble, but the append test not
only
Post by Ana Emília M. Arruda
Post by Steve Garcia
fails, but it takes the tape drive offline. Once this happens, the
drive
Post by Ana Emília M. Arruda
Post by Steve Garcia
is not accessible until the tape is physically dismounted and then
remounted. Once this happens, the drive comes back to life, but it
will go
Post by Ana Emília M. Arruda
Post by Steve Garcia
offline again if the append test is re-attempted.
The btape failure message suggested using a fixed block size, but
making
Post by Ana Emília M. Arruda
Post by Steve Garcia
that change didn't seem to make any difference.
I tried downloading the IBM ITDT utility and running all its tests, but
the drive passed with flying colors in the ITDT diagnostics.
I am running bacula 7.4.4 on a new Debian stretch (Debian 9) server
with a
Post by Ana Emília M. Arruda
Post by Steve Garcia
new tape library and tape drive. The new drive is an IBM ULT3580-HH6
LTO-6
Post by Ana Emília M. Arruda
Post by Steve Garcia
drive in a Dell TL-2000 library. I have an existing bacula instance
running on a Debian jesse (debian 8) server, and my plan is to add the
new
Post by Ana Emília M. Arruda
Post by Steve Garcia
tape library as an additional pool for the existing instance. For now,
though, unless I can get the drive to work with bacula, planning how
to set
Post by Ana Emília M. Arruda
Post by Steve Garcia
bacula itself up doesn't matter.
What steps can I do to troubleshoot this?
One thing I notice is that lsscsi shows the tape drive twice, but
there is
Post by Ana Emília M. Arruda
Post by Steve Garcia
only one actual drive. Could this be a part of the problem?
Loading media from Storage Element 1 into drive 0...done
D:0:F:1:000015L6
S:1:E
S:2:F:000018L6
S:3:F:000021L6
S:4:F:CLNU00L1
S:5:F:000014L6
S:6:F:000017L6
S:7:F:000020L6
S:8:F:CLN005L3
S:9:F:000013L6
S:10:F:000016L6
S:11:F:000019L6
S:12:F:000012L6
S:13:F:000009L6
S:14:F:000006L6
S:15:F:000003L6
S:16:F:000011L6
S:17:F:000008L6
S:18:F:000005L6
S:19:F:000002L6
S:20:F:000010L6
S:21:F:000007L6
S:22:F:000004L6
S:23:F:000001L6
I:24:E
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
test
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*
=== 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:1154-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1170-0 Wrote 10000 blocks of 64412 bytes.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1212-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:1279-0 Block position test
btape: btape.c:1291-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 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:576-0 Rewound "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:1909-0 Wrote one record of 64412 bytes.
btape: btape.c:1911-0 Wrote block to device.
btape: btape.c:606-0 Wrote 1 EOF to "Drive-1" (/dev/nst0)
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/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
btape: btape.c:573-0 Bad status from rewind. ERR=tape_dev.c:164 Unable
to
Post by Ana Emília M. Arruda
Post by Steve Garcia
open device "Drive-1" (/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: block.c:144-0 Attempt to write on read-only Volume.
dev="Drive-1"
Post by Ana Emília M. Arruda
Post by Steve Garcia
(/dev/nst0)
13-Jul 16:07 btape JobId 0: Fatal error: block.c:144 Attempt to write
on
Post by Ana Emília M. Arruda
Post by Steve Garcia
read-only Volume. dev="Drive-1" (/dev/nst0)
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call
to
Post by Ana Emília M. Arruda
Post by Steve Garcia
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call
to
Post by Ana Emília M. Arruda
Post by Steve Garcia
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: btape.c:1906-0 Error writing block to device.
tape_dev.c:917 Bad call to weof_dev. Device not open
tape_dev.c:917 Bad call to weof_dev. Device not open
btape: btape.c:602-0 Bad status from weof. ERR=tape_dev.c:917 Bad call
to
Post by Ana Emília M. Arruda
Post by Steve Garcia
weof_dev. Device not open
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
That appears *NOT* to have corrected the problem.
Append test failed.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Unable to correct the problem. You MUST fix this
problem before Bacula can use your tape drive correctly
Perhaps running Bacula in fixed block mode will work.
Minimum Block Size = nnn
Maximum Block Size = nnn
in your Storage daemon's Device definition.
nnn must match your tape driver's block size, which
can be determined by reading your tape manufacturers
information, and the information on your kernel dirver.
Fixed block sizes, however, are not normally an ideal solution.
Some systems, e.g. OpenBSD, require you to set
Use MTIOCGET= no
in your device resource. Use with caution.
*quit
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
dev open failed: tape_dev.c:164 Unable to open device "Drive-1"
(/dev/nst0): ERR=Input/output error
btape: butil.c:199-0 Cannot open "Drive-1" (/dev/nst0)
13-Jul 16:10 btape JobId 0: Fatal error: butil.c:199 Cannot open
"Drive-1"
Post by Ana Emília M. Arruda
Post by Steve Garcia
(/dev/nst0)
1
Post by Ana Emília M. Arruda
Post by Steve Garcia
/dev/nst0 0
Unloading drive 0 into Storage Element 1...done
Loading media from Storage Element 1 into drive 0...done
Tape block granularity is 1024 bytes.
btape: butil.c:291-0 Using device: "/dev/nst0" for writing.
btape: btape.c:471-0 open device "Drive-1" (/dev/nst0): OK
*
[0:2:0:0] disk DELL PERC H730 Mini 4.27 /dev/sda
/dev/sg0
Post by Ana Emília M. Arruda
Post by Steve Garcia
[1:0:0:0] tape IBM ULT3580-HH6 G9P1 /dev/st0
/dev/sg2
Post by Ana Emília M. Arruda
Post by Steve Garcia
[1:0:0:1] mediumx IBM 3573-TL E.30 /dev/sch0
/dev/sg3
Post by Ana Emília M. Arruda
Post by Steve Garcia
[1:0:1:0] tape IBM ULT3580-HH6 G9P1 /dev/st1
/dev/sg4
Post by Ana Emília M. Arruda
Post by Steve Garcia
[1:0:1:1] mediumx IBM 3573-TL E.30 /dev/sch1
/dev/sg5
Post by Ana Emília M. Arruda
Post by Steve Garcia
[6:2:0:0] disk DELL PERC H830 Adp 4.27 /dev/sdb
/dev/sg1
Post by Ana Emília M. Arruda
Post by Steve Garcia
[12:0:0:0] cd/dvd PLDS DVD-ROM DS-8DBSH MD52 /dev/sr0
/dev/sg6
Post by Ana Emília M. Arruda
Post by Steve Garcia
Product Type: Tape Drive
Vendor ID: 'IBM '
Product ID: 'ULT3580-HH6 '
Revision: 'G9P1'
Attached Changer API: No
SerialNumber: '10WT110956'
MinBlock: 1
MaxBlock: 8388608
SCSI ID: 0
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: 0x68
Density Code: 0x5a
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0xff
DeCompType: 0xff
BOP: yes
Block Position: 0
Partition 0 Remaining Kbytes: -1
Partition 0 Size in Kbytes: -1
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 3
Device {
Name = Drive-1 #
Description = "LT06 inside Dell TL2000 Library"
Drive Index = 0
Media Type = LT06
Archive Device = /dev/nst0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
SpoolDirectory = "/var/spool/bacula"
MaximumSpoolSize = 485G
Maximum Network Buffer Size = 65536
# MaximumBlockSize = 256k
# MinimumBlockSize = 256k
Offline On Unmount = yes
# #
# # Enable the Alert command only if you have the mtx package loaded
# # Note, apparently on some systems, tapeinfo resets the SCSI
controller
Post by Ana Emília M. Arruda
Post by Steve Garcia
# # thus if you turn this on, make sure it does not reset your SCSI
# # controller. I have never had any problems, and smartctl does
# # not seem to cause such problems.
# #
#Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
# If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = "sh -c 'smartctl -H -l error %c'"
}
--
Steve Garcia
Ignorance killed the cat, curiosity was framed.
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
https://lists.sourceforge.net/lists/listinfo/bacula-users
Loading...