Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 May 2010 09:29:31 +0200
From:      Holm Tiffe <holm@freibergnet.de>
To:        Matthew Jacob <mj@feral.com>
Cc:        freebsd-scsi@freebsd.org
Subject:   Re: Problems with DLT on 8-Stable
Message-ID:  <20100518072931.GA10575@pegasus.freiberg-net.de>
In-Reply-To: <4BF1A7DB.9020203@feral.com>
References:  <20100517150513.GA93298@pegasus.freiberg-net.de> <4BF16C62.6010104@feral.com> <20100517175923.GA96425@pegasus.freiberg-net.de> <4BF189BE.9000008@feral.com> <20100517200856.GB96425@pegasus.freiberg-net.de> <4BF1A429.501@feral.com> <20100517203031.GA98817@pegasus.freiberg-net.de> <4BF1A7DB.9020203@feral.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Jacob wrote:

> Holm Tiffe wrote:
> >Matthew Jacob wrote:
> >
> >Huh? Im not a browser...
> >
> >
> >What do you have against the Tandberg drive?
> >This old thing has done a good job in the years before.
> >  
> 
> It's a QIC drive, with fixed 512 byte sectors formatted on tape. The 
> Tandberg guys thought that they could impose variable length records on 
> top of that. I have large memories of  pain, but the details have been lost.
> 
> Hey, if it works for you....

Tandberg has many different kinds of firmware for the drives,
and there are several QIC Models, 250mb,525mb,2,5G,5G,8G...
The drive in my PC has flawlessly worked the years before,
but I remeber that there where problems on older drives.
But the Tandbergs have a working mechanic in difference to
the Wangteks or similar..


It seems, ithat here is not that much difference to the DLT:

# mt -f /dev/sa0.ctl status
Mode      Density              Blocksize      bpi      Compression
Current:  0x15:ECMA TC17       variable       45434    disabled
---------available modes---------
0:        0x15:ECMA TC17       variable       45434    0x3
1:        0x15:ECMA TC17       variable       45434    0x3
2:        0x15:ECMA TC17       variable       45434    0x3
3:        0x15:ECMA TC17       variable       45434    0x3
---------------------------------
Current Driver State: at rest.
---------------------------------
File Number: 2  Record Number: 0        Residual Count 0

(Magnum 1.2 Gig tape inserted)

besides of that, the drive behaves exactly the same as the DLT.

  DUMP: 2.40% done, finished in 27:04 at Wed May 19 11:50:21 2010
  DUMP: 2.70% done, finished in 27:00 at Wed May 19 11:51:33 2010
  DUMP: 3.00% done, finished in 26:56 at Wed May 19 11:52:02 2010
  DUMP: End of tape detected
  DUMP: Closing /dev/nsa0
  DUMP: Change Volumes: Mount volume #2
  DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") yes
  DUMP: Volume 2 begins with blocks from inode 2779313
  DUMP: EOT detected at start of the tape!
  DUMP: The ENTIRE dump is aborted.

Dump detects that EOT before it is reading a byte from the drive,
eg there are no transport noises after changing the tape and typing in
"yes". After that, the tape moves a little around...

At least the Tandberg drive has cleared now that the problem is not
related to the DLT drive itself. And now?

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@tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100518072931.GA10575>