--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
--- Begin Message ---
Thanks, Darren,
This was helpful. After a few more backups (no configuration changes),
things are looking up.
We had one tape fill up at 372 GB and two others at 440 and 445 GB
respectively, so I guess I was too
quick on the draw, *BUT* I ran the stinit command as 'stinit -v -v' (see
output below), and I have two questions:
1. Since stinit reports 4 modes from 0-3, but our stinit.def file
numbers these modes from 1-4, SHOULD
I edit the stinit.def file to match this so it, too, numbers them from
0-3, or does stinit figure that out?
Again, I'm using /dev/nst0, 1, 2 and 3 for my 4 devices, but if stinit
thinks this each of those is mode 0 then how could
it be assigning it properly if the stinit.def file doesn't have a line
for mode 0?
When I run 'mt -f /dev/nst0 status' against drive 1, with a loaded
NetWorker labeled tape, it reports code 0x4a, so it's obviously picking
up one
of the first 2 lines from the stinit.def file, and since we're seeing
more than 300 GB on some tapes I would think it must be using line 1
(mode 1).
2. We've done NetWorker recovers on these new SDLT 600 drives using
older SDLT 1 tapes that were written on SDLT 220 drives,
Everything works fine, but the device names were still /dev/nst0, 1, 2
and 3. If stinit does think this is mode 1 how was
it able to read the tape since I didn't use /dev/nst0a (mode 4)? Does it
know to jump down to the 220 definition and use
the mode 1 listed there instead of the mode 4 listed under the 600
definition?
sample stinit.def entry for SDLT
-------------------------------------------
# QUANTUM SDLT600
manufacturer=QUANTUM model="SDLT600" {
timeout=3600 # 1 hour timeout
long-timeout=14400 # 4 hour long timeout
can-partitions=0
mode1 blocksize=0 density=0x4A compression=1 # SDLT600 density,
compression on
mode2 blocksize=0 density=0x4A compression=0 # SDLT600 density,
compression off
mode3 blocksize=0 density=0x49 compression=1 # SDLT320 density,
compression on
mode4 blocksize=0 density=0x48 compression=1 # SDLT220 density,
compression on
}
# QUANTUM SDLT220
manufacturer=QUANTUM model="SuperDLT1" {
timeout=3600
long-timeout=14400
can-partitions=0
mode1 blocksize=0 density=0x48 compression=1 # SDLT220 density,
compression on
mode2 blocksize=0 density=0x48 compression=0 # SDLT220 density,
compression off
mode3 blocksize=0 density=0x41 compression=1 # DLT8000 density,
compression on
mode4 blocksize=0 density=0x41 compression=0 # DLT8000 density,
compression off
}
output from stinit -v -v
---------------------------------------------------------------------
Trying to open database '/etc/stinit.def'.
Open succeeded.
stinit, processing tape 0
Mode 0, name '/dev/nst0'
Mode 1, name '/dev/nst0l'
Mode 2, name '/dev/nst0m'
Mode 3, name '/dev/nst0a'
The manufacturer is 'QUANTUM', product is 'SDLT600', and revision '2929'.
Mode 1 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=1
Mode 2 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=0
Mode 3 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x49 compression=1
Mode 4 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x48 compression=1
stinit, processing tape 1
Mode 0, name '/dev/nst1'
Mode 1, name '/dev/nst1l'
Mode 2, name '/dev/nst1m'
Mode 3, name '/dev/nst1a'
The manufacturer is 'QUANTUM', product is 'SDLT600', and revision '2929'.
Mode 1 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=1
Mode 2 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=0
Mode 3 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x49 compression=1
Mode 4 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x48 compression=1
stinit, processing tape 2
Mode 0, name '/dev/nst2'
Mode 1, name '/dev/nst2l'
Mode 2, name '/dev/nst2m'
Mode 3, name '/dev/nst2a'
The manufacturer is 'QUANTUM', product is 'SDLT600', and revision '2929'.
Mode 1 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=1
Mode 2 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=0
Mode 3 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x49 compression=1
Mode 4 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x48 compression=1
stinit, processing tape 3
Mode 0, name '/dev/nst3'
Mode 1, name '/dev/nst3l'
Mode 2, name '/dev/nst3m'
Mode 3, name '/dev/nst3a'
The manufacturer is 'QUANTUM', product is 'SDLT600', and revision '2929'.
Mode 1 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=1
Mode 2 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x4A compression=0
Mode 3 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x49 compression=1
Mode 4 definition: timeout=3600 long-timeout=14400 can-partitions=0
blocksize=0 density=0x48 compression=1
stinit, processing tape 4
Mode 0, name '/dev/nst4'
Mode 1, name '/dev/nst4l'
Mode 2, name '/dev/nst4m'
Mode 3, name '/dev/nst4a'
Device '/dev/nst4' not found by kernel.
Initialized 4 tape devices.
Darren Dunham wrote:
Quantum M1800 tape library with
four SDLT 600 drives, attached via SCSI to a Linux storage node server.
When I ran jbconfig, I specified
/dev/nst# where # was 0-3 for each device. I'm wondering what these
other modes do, and if maybe I should
be using one of those instead. I'm able to backup and recover fine to
these drives, but compression rates
seem low. Here are some of the volumes we've written to:
volume (%used) written
[...]
FLN027 65% 195 GB
INC001 full 329 GB
INC002 full 346 GB
INC003 full 292 GB
INC004 full 349 GB
INC005 100% 355 GB
> I thought SDLT II tapes were 300/600. With our old ATL P1000 library
that has SDLT 220 drives it was not uncommon to get
135-160+ GB on a SDLT 1 tape. That's nearly 1.5 times the 110 native
capacity on average. I'm not seeing anything near 1.5 times
(let alone twice) the capacity of the SDLT II tapes, however. That would
be 450 GB.
Yup, but the driver isn't going to control the compression algorithm or
anything like that. If you're getting anything above the native
capacity, then it must at least be enabling compression.
I copied the stinit.def file template from Quantum's site, and copied it
to /etc/stinit.def. It has the
following entry for the SDLT600:
# QUANTUM SDLT600
manufacturer=QUANTUM model="SDLT600" {
timeout=3600 # 1 hour timeout
long-timeout=14400 # 4 hour long timeout
can-partitions=0
mode1 blocksize=0 density=0x4A compression=1 # SDLT600 density,
compression on
mode2 blocksize=0 density=0x4A compression=0 # SDLT600 density,
compression off
mode3 blocksize=0 density=0x49 compression=1 # SDLT320 density,
compression on
mode4 blocksize=0 density=0x48 compression=1 # SDLT220 density,
compression on
}
There's your 0, 0l, 0m and 0a devices. You certainly want to be using
mode 1. Here's a page that mentions 'stinit -v -v' should show that
association more explicitly (although this file is 1-4 and the other bit
of output is 0-3, I think they should line up).
http://www.mail-archive.com/linux-setup AT senator-bedfellow.mit DOT
edu/msg03128.html
So am I to assume that nst0, 1, 2 and 3 would use mode 1, and nst0a
would used mode 2 and
nst0l would use mode 3 and then nst0m would use mode 4? How do you know
which mode
is assigned to which device: nst0, a, l or m? Are we correct to be using
nst0, 1, 2 and 3 then for hardware compression?
That's my understanding.
--
George Sinclair - NOAA/NESDIS/National Oceanographic Data Center
SSMC3 4th Floor Rm 4145 | Voice: (301) 713-3284 x210
1315 East West Highway | Fax: (301) 713-3301
Silver Spring, MD 20910-3282 | Web Site: http://www.nodc.noaa.gov/
- Any opinions expressed in this message are NOT those of the US Govt. -
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the body of the email. Please write to networker-request
AT listserv.temple DOT edu if you have any problems with this list. You can access the
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
--- End Message ---
|
