SUMMARY: sdlt320 tape drive under 5.1b (ddr.dbase entry)

From: curt steinmetz (curt@cola.iges.org)
Date: Wed Aug 20 2003 - 16:00:04 EDT


Johan Brusche was kind enough to send the entry.
Thanks! He also suggested looking on the docs CD,
but all I could find there was the "technical update",
not the release notes (which is also the case with
the on-line documentation I was able to find on the
website).

Here's the entry:

          csi_density_table_size = 0x4a

         scsi_tape_density[0x42] = "density_code_42" 0
0
         scsi_tape_density[0x43] = "density_code_43" 0
0
         scsi_tape_density[0x44] = "density_code_44" 0
0
         scsi_tape_density[0x45] = "density_code_45" 0
0
         scsi_tape_density[0x46] = "density_code_46" 0
0
         scsi_tape_density[0x47] = "density_code_47" 0
0
         scsi_tape_density[0x48] = "131000_bpi" 131000
0
         scsi_tape_density[0x49] = "190000_bpi" 190000
0

         SCSIDEVICE
         #
         # Matches SDLT320
         #
         Type = tape
         Name = "COMPAQ" "SDLT320"
         #
         #
         PARAMETERS:
         TypeSubClass = tk
         TagQueueDepth = 0
         MaxTransferSize = 0x0fffffb # (16MB - 4)
         ReadyTimeSeconds = 120 # seconds

         DENSITY:
         #
         DensityNumber = 0
         DensityCode = 0x48
         CompressionCode = 0x1
         Buffered = 0x1

         DENSITY:
         #
         DensityNumber = 1,5
         DensityCode = default
         CompressionCode = 0x1
         Buffered = 0x1

         DENSITY:
         #
         DensityNumber = 2,4,6,7
         DensityCode = default
         CompressionCode = 0x0
         Buffered = 0x1

         DENSITY:
         #
         DensityNumber = 3
         DensityCode = 0x48
         CompressionCode = 0x0
         Buffered = 0x1

On Tuesday, August 19, 2003, at 10:37 AM, curt steinmetz wrote:

> Is there any way around manually typing in the whole
> danged entry for an sdlt320 drive in ddr.dbase? The
> release notes for 5.1b (section 5.3.1) states: "insert
> the following density information and SCSIDEVICE entry"
> (into the ddr.dbase file). Its a lot of stuff to type in, and
> it seems quite an inefficient and error prone way to
> proceed. If there was even an online version of the
> release notes I could just cut and paste it.
> The drive seems to work "OK" without this entry - but
> it does print out warning messages. Since I am using
> this drive to back up everyone's home directories and
> the most important system files on our main file server,
> I do not want to take any chances!
> - Curt



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:33 EDT