Gene Heskett wrote:
On Monday 16 June 2003 09:22, Junaidi wrote:
luke root # mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x40 (DLT1 40 GB, or Ultrium).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
...
And I'm finding out that the defblksize must be the same at read time
as it was at write time here, else amanda cannot read the labels at
Yes, unless you have variable blocksize, in that case reading with
a blocksize (in the program, not in the tapedriver!) equal to or larger
than what the one on tape works fine (when I try it on my DDS2 and AIT1
drive, in my environment).
all. Also, I'm noteing that the above reported blocksize is 0, but
here on a linux box, I cannot set it below 1 byte unless I use that
specifically. And empty number arguement sets it to 1. Kernel is
2.4.21.
blocksize 0 means variable blocksize.
I can set it without problems. Kernel 2.4.18 (stock redhat 8)
and kernel 2.4.20 (compiled myself) here. When I was using 2.2.19
it worked fine too.
I was trying to find out if the blocksize (or something else) changed
between writing and reading the label. That's why I asked a
'mt status' before and after the amlabel command (without touching
the drive!).
--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
