Hi Jean-Louis,
Thanks for clarifying that. Interesting to see that the '-f' option for amlabel
overrides the
readblocksize.
I got an error reading 512MiB but found a threshold at 1MiB where I could read
the tape:
dd if=/dev/rmt/0bn bs=1024K count=1 of=/dev/null
0+1 records in
0+1 records out
32
Tom,
You can define the block size as the BLOCK-SIZE device property in the
changer section or in the tapetype, the device-property is used if it is
set.
You can define the read_block_size as the READ-BLOCK-SIZE device
property in the changer section or in the tapetype, the device-property
Sorry, I didn't mentioned that the IBM tape device accepts LTO 5 media.
$ mt config
"IBM ULT3580-TD5", "IBM ULT3580-TD5 ", "CFGIBMULT3580TD5";
CFGIBMULT3580TD5 =
2,0x3B,0,0x1018619,4,0x46,0x46,0x58,0x58,3,60,1500,600,16920,780,780,16380;
$ mt status
IBM ULT3580-TD5 tape driv
Amanda 3.3.3
OmniOS (OpenSolaris derivative)
Hi,
I've got an IBM TS3200 robot working with mtx. The raw mtx command sees the
robot and tapes OK but
when I use amtape I get a 'block size too small' error.
The amlabel command also fails with:
$ amlabel weekly weekly00 slot 1
Reading label...
Err
