Problems with DLT on 8-Stable

[Holm Tiffe]

Matthew Jacob wrote:

> Holm Tiffe wrote:
> >You can get what you ever want, but there is no message in
> >/var/log/messages regarding this.
> >  
> The messages state a "Media Not Present" error, on top of two TUR 
> conditions.

Did you mean this:

(probe6:ahc0:0:6:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe6:ahc0:0:6:0): CAM status: SCSI Status Error
(probe6:ahc0:0:6:0): SCSI status: Check Condition
(probe6:ahc0:0:6:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset,
or bu
s device reset occurred)
(probe5:ahc0:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe5:ahc0:0:5:0): CAM status: SCSI Status Error
(probe5:ahc0:0:5:0): SCSI status: Check Condition
(probe5:ahc0:0:5:0): SCSI sense: UNIT ATTENTION asc:29,0 (Power on, reset,
or bu
s device reset occurred)
(probe5:ahc0:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe5:ahc0:0:5:0): CAM status: SCSI Status Error
(probe5:ahc0:0:5:0): SCSI status: Check Condition
(probe5:ahc0:0:5:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
sa0 at ahc0 bus 0 scbus0 target 5 lun 0
sa0: <TANDBERG SLR5 4/8GB =09:> Removable Sequential Access SCSI-2 device 
sa0: 3.300MB/s transfers

If so, no, that has nothing todo with the DLT or the dump,
0:5:0 is a Tandberg QIC Streamer and the message was appearing while
booting (/var/run/dmesg.boot)

# camcontrol devlist
<IBM-SSG S53D073 C61E>             at scbus0 target 0 lun 0 (da0,pass0)
<IBM-SSG S53D073 C61E>             at scbus0 target 1 lun 0 (da1,pass1)
<IBM-SSG S53D073 C61A>             at scbus0 target 2 lun 0 (da2,pass2)
<IBM-SSG S53D073 C61A>             at scbus0 target 3 lun 0 (da3,pass3)
<TANDBERG SLR5 4/8GB =09:>         at scbus0 target 5 lun 0 (sa0,pass4)
<Quantum DLT4000 CC28>             at scbus0 target 6 lun 0 (sa1,pass5)

> 
> Do any of these correlate to you changing the tapes?

No.
There is nothing on console or /var/log/messages after changing the tape.
It is simple dump that complains there where an EOT on the new inserted
tape.
> 
> The '65536-byte tape record' message  is interesting. For some reason, 
> sa is receiving a write that is no 64K in size, and the tape is in 
> 'fixed' 64K block mode.

Hmm, I think the other way around.
I've wrote 64K blocks with the last dump on the tape and somebody is trying
to read with a smaller buffer....

Remember, I do dumps like this:
dump L0uaf /dev/nsa1  -b 64 -C 16 /data

where b is the Blocksize in k and C is the Cache size in Meg.
> 
> Can you send the output of 'mt -f /dev/nsa1 status' with a tape loaded.

# mt -f /dev/nsa1 status
Mode      Density              Blocksize      bpi      Compression
Current:  0x1a:DLTapeIV(20GB)    variable       81633    IDRC
---------available modes---------
0:        0x1a:DLTapeIV(20GB)    variable       81633    IDRC
1:        0x1a:DLTapeIV(20GB)    variable       81633    IDRC
2:        0x1a:DLTapeIV(20GB)    variable       81633    IDRC
3:        0x1a:DLTapeIV(20GB)    variable       81633    IDRC
---------------------------------
Current Driver State: at rest.
---------------------------------
File Number: 1  Record Number: 0        Residual Count 0

> 
> More than that I'll have to dig up a tape drive and attach it- I haven't 
> used on on FreeBSD in years.

I'll test this on the old trusty Tandberg 8Gig QIC drive tomorrow and will
post the results.

Kind Regards,

Holm

-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741