RE: HP DLT1e tapetype
Hi all,
Sorry about posting the HW compression version first (especially to anyone who
searches the archives). I read more on st.conf (yes it's running under Solaris 8) and
played some with the various options. Here is what I got when I used the correct
device:
$amtapetype -e 40g -f /dev/rmt/0ln -t HP-DLT1e
Estimated time to write 2 * 40960 Mbyte: 30720 sec = 8 h 32 min
wrote 1232058 32Kb blocks in 94 files in 13969 seconds (short write)
wrote 1238517 32Kb blocks in 189 files in 14193 seconds (short write)
define tapetype HP-DLT1e {
comment just produced by tapetype prog (hardware compression off)
length 38602 mbytes
filemark 0 kbytes
speed 2807 kps
}
Now to actually try a backup.
Re: HP DLT1e tapetype [Solaris density/compression defaults]
On Thu, Jun 19, 2003 at 11:47:53PM -0400, Jon LaBadie wrote: I'm not sure what documentation you're referring to, but for every compression-capable drive I've ever used (DDS2, DDS3, DLT-4000, DLT-7000, DLT-8000, LTO-1) both the Solaris factory st driver and the tape-vendor-supplied st.conf default to the highest-possible density and compression factor. Actually Jay the default can be specified in the st.conf file to match any of the l, m, h, or u/c entries and for 15 of the 49 entries in my file the default does not correspond to the u/c mode. Jon, you are exactly right, and I was... not. :-) In my (meager) defense, I did also mention tape-vendor-supplied st.conf default, and for example, the Quantum DLT/Solaris recommendation is: From: http://www.quantum.com/AM/support/DLTtapeDrivesMedia/TechnicalDocuments/Default.htm Where the Solaris install PDF does explain all the funky mode bits, If you are installing a DLT4000 add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x17, 0x18, 0x82, 0x83, 3; If you are installing a DLT7000 add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x82, 0x83, 0x84, 0x85, 3; If you are installing a DLT8000 add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x84, 0x85, 0x88, 0x89, 3; If you are installing a Super DLTtape add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x90, 0x91, 0x90, 0x91, 3; This is what I'm currently using for DLT, and it does default to max density/compression, FWIW. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: HP DLT1e tapetype [Solaris density/compression defaults]
On Fri, Jun 20, 2003 at 10:18:39AM -0700, Jay Lessert wrote: ... for example, the Quantum DLT/Solaris recommendation is: From: http://www.quantum.com/AM/support/DLTtapeDrivesMedia/TechnicalDocuments/Default.htm Where the Solaris install PDF does explain all the funky mode bits, If you are installing a DLT4000 add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x17, 0x18, 0x82, 0x83, 3; If you are installing a DLT7000 add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x82, 0x83, 0x84, 0x85, 3; If you are installing a DLT8000 add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x84, 0x85, 0x88, 0x89, 3; If you are installing a Super DLTtape add the following line: DLTtape data = 1, 0x38, 0, 0x8639, 4, 0x90, 0x91, 0x90, 0x91, 3; Amazing. I guess Quantum thinks no one will ever have more than one type of DLT drive installed at the same time. Seems like it would be more efficient to put all of them in at one time and give each a different DLTtape data label. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: HP DLT1e tapetype [Solaris density/compression defaults]
On Fri, Jun 20, 2003 at 01:28:04PM -0400, Jon LaBadie wrote: On Fri, Jun 20, 2003 at 10:18:39AM -0700, Jay Lessert wrote: From: http://www.quantum.com/AM/support/DLTtapeDrivesMedia/TechnicalDocuments/Default.htm Where the Solaris install PDF does explain all the funky mode bits, Amazing. I guess Quantum thinks no one will ever have more than one type of DLT drive installed at the same time. Seems like it would be more efficient to put all of them in at one time and give each a different DLTtape data label. Yeah, I'm not complaining too much. The referenced PDF is the best Solaris tape drive install doc I've ever seen; it actually explicitly defines all the density codes, so you know exactly what you're getting. I don't mind editing a few characters in the data property names... -Jay-
Re: HP DLT1e tapetype
On Thursday 19 June 2003 11:51, Ean Kingston wrote:
I couldn't find this one in the list archvies, so here it is.
I'm using 40GB DLT tapes (according to the label). Despite what the
comment produced says, I used the non-compressed device. I didn't
give it an estimate for the tapesize.
Writing 256 Mbyte compresseable data: 34 sec
Writing 256 Mbyte uncompresseable data: 105 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 1024 Mbyte: 840 sec = 0 h 14 min
wrote 1102644 32Kb blocks in 3372 files in 21817 seconds (short
write) wrote 1101228 32Kb blocks in 6756 files in 29828 seconds
(short write) define tapetype HP-DLT1e {
comment just produced by tapetype prog (hardware compression
on) length 34499 mbytes
filemark 13 kbytes
speed 1399 kps
}
And it appears the hardware compressor being on cost you 5.5 gigs.
The various 'tapetype' programs all use the output of /dev/urandom as
the data source, and the output of /dev/urandom is not compressible,
and will in fact grow by about the percentage you see above in being
passed thru the hardware compressor.
As others have noted Ean, you can turn it off, but this must be done
for every new tape thats inserted as the recognition phase of the
drive will turn it back on when the tapes are changed. Such info as
how to turn it on/off should be on the drive makers web page. To
your vendor its obviously not a very high priority to obtain that
info for you else he would have fired up a browser and found it on
the spot.
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
RE: HP DLT1e tapetype
-Original Message-
On Thursday 19 June 2003 11:51, Ean Kingston wrote:
I couldn't find this one in the list archives, so here it is.
I'm using 40GB DLT tapes (according to the label). Despite what the
comment produced says, I used the non-compressed device. I didn't
give it an estimate for the tapesize.
Writing 256 Mbyte compresseable data: 34 sec
Writing 256 Mbyte uncompresseable data: 105 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 1024 Mbyte: 840 sec = 0 h 14 min
wrote 1102644 32Kb blocks in 3372 files in 21817 seconds (short
write) wrote 1101228 32Kb blocks in 6756 files in 29828 seconds
(short write) define tapetype HP-DLT1e {
comment just produced by tapetype prog (hardware compression
on) length 34499 mbytes
filemark 13 kbytes
speed 1399 kps
}
And it appears the hardware compressor being on cost you 5.5 gigs.
The various 'tapetype' programs all use the output of /dev/urandom as
the data source, and the output of /dev/urandom is not compressible,
and will in fact grow by about the percentage you see above in being
passed thru the hardware compressor.
As others have noted Ean, you can turn it off, but this must be done
for every new tape that's inserted as the recognition phase of the
drive will turn it back on when the tapes are changed. Such info as
how to turn it on/off should be on the drive makers web page. To
your vendor its obviously not a very high priority to obtain that
info for you else he would have fired up a browser and found it on
the spot.
I'm using Solaris and, according to the documentation, it should not be using hardware
compression unless I specify the 'compress' device (/dev/rmt/0cn) as opposed to the
one I did use (/dev/rmt/0n). If what you say it true there is some way to force HW
compression for the tape drive regardless of what the OS wants.
Re: HP DLT1e tapetype
On Thursday 19 June 2003 14:09, Ean Kingston wrote:
-Original Message-
On Thursday 19 June 2003 11:51, Ean Kingston wrote:
I couldn't find this one in the list archives, so here it is.
I'm using 40GB DLT tapes (according to the label). Despite what
the comment produced says, I used the non-compressed device. I
didn't give it an estimate for the tapesize.
Writing 256 Mbyte compresseable data: 34 sec
Writing 256 Mbyte uncompresseable data: 105 sec
WARNING: Tape drive has hardware compression enabled
Estimated time to write 2 * 1024 Mbyte: 840 sec = 0 h 14 min
wrote 1102644 32Kb blocks in 3372 files in 21817 seconds (short
write) wrote 1101228 32Kb blocks in 6756 files in 29828 seconds
(short write) define tapetype HP-DLT1e {
comment just produced by tapetype prog (hardware compression
on) length 34499 mbytes
filemark 13 kbytes
speed 1399 kps
}
And it appears the hardware compressor being on cost you 5.5 gigs.
The various 'tapetype' programs all use the output of /dev/urandom
as the data source, and the output of /dev/urandom is not
compressible, and will in fact grow by about the percentage you
see above in being passed thru the hardware compressor.
As others have noted Ean, you can turn it off, but this must be
done for every new tape that's inserted as the recognition phase
of the drive will turn it back on when the tapes are changed.
Such info as how to turn it on/off should be on the drive makers
web page. To your vendor its obviously not a very high priority
to obtain that info for you else he would have fired up a browser
and found it on the spot.
I'm using Solaris and, according to the documentation, it should not
be using hardware compression unless I specify the 'compress'
device (/dev/rmt/0cn) as opposed to the one I did use
(/dev/rmt/0n). If what you say it true there is some way to force
HW compression for the tape drive regardless of what the OS wants.
I'll leave that pronouncement to the Sol experts here, like Jon
LaBadie.
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: HP DLT1e tapetype
On Thursday 19 June 2003 14:09, Ean Kingston wrote: I'm using Solaris and, according to the documentation, it should not be using hardware compression unless I specify the 'compress' device (/dev/rmt/0cn) as opposed to the one I did use (/dev/rmt/0n). I'm not sure what documentation you're referring to, but for every compression-capable drive I've ever used (DDS2, DDS3, DLT-4000, DLT-7000, DLT-8000, LTO-1) both the Solaris factory st driver and the tape-vendor-supplied st.conf default to the highest-possible density and compression factor. That is, I would be *very* surprised if the 0n device for your DLT1 drive doesn't do 80GB (compressed) mode. I've not used DLT1 myself, but if you show us the st.conf you're using we can confirm/deny... -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
Re: HP DLT1e tapetype
On Thu, Jun 19, 2003 at 04:14:38PM -0700, Jay Lessert wrote: On Thursday 19 June 2003 14:09, Ean Kingston wrote: I'm using Solaris and, according to the documentation, it should not be using hardware compression unless I specify the 'compress' device (/dev/rmt/0cn) as opposed to the one I did use (/dev/rmt/0n). I'm not sure what documentation you're referring to, but for every compression-capable drive I've ever used (DDS2, DDS3, DLT-4000, DLT-7000, DLT-8000, LTO-1) both the Solaris factory st driver and the tape-vendor-supplied st.conf default to the highest-possible density and compression factor. Actually Jay the default can be specified in the st.conf file to match any of the l, m, h, or u/c entries and for 15 of the 49 entries in my file the default does not correspond to the u/c mode. device letter l m hu/c 0 1 2 3 ANRITSU ... 0x00, 0x02 ,0x03, 0x03, 1; C3490 ... 0x00, 0x00, 0x00, 0x01, 2; DLT ... 0x17, 0x18, 0x80, 0x81, 2; DLT-data ... 0x80, 0x81, 0x82, 0x83, 2; DLT7k-data... 0x82, 0x83, 0x84, 0x85, 2; Exa8500c ... 0x14, 0x15, 0x8C, 0x8C, 1; Exa8505 ... 0x14, 0x15, 0x90, 0x8c, 1; EXB-8500 ... 0x14, 0x15, 0x8C, 0x8C, 1; Fujitsu_comp ... 0x00, 0x00, 0x00, 0x09, 1; HP_half ... 0x01, 0x02, 0x03, 0xC3, 1; HPT4 ... 0x45, 0x00, 0x00, 0x00, 0; KENNEDY ... 0x01, 0x02, 0x03, 0x03, 1; M4_DATA ... 0x01, 0x02, 0x06, 0x06, 1; MT02 ... 0x84, 0x05, 0x05, 0x05, 1; TAND-50G-VAR ... 0x30, 0x00, 0x00, 0x00, 0; The last column specifies which of the 4 densities corresponds to the 0 device (without l,m,h,c, or u). That is, I would be *very* surprised if the 0n device for your DLT1 drive doesn't do 80GB (compressed) mode. I think the numeric values in columns 0 - 3 above are parameters passed to the st driver when the drive is opened. A long time ago I saw some HP DAT drive docs that said each bit in the values corresponded to a parameter like compression ... You would need similar docs from the drive manufacturer to decipher the numeric values. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
