[Networker] INCORRECT BLOCK SIZE / DRIVE FAIL?
2004-10-04 10:00:31
I had an event like this about half a year ago, but this one is new.
Does anyone want to venture an opinion about whether this is a hardware
(i.e. library) or software (networker) problem?
Environment:
First, note that the setup I have has been working flawlessly
for 6 months.
Linux tapes.dfci.harvard.edu 2.4.20-31.9 #1
Tue Apr 13 18:04:23 EDT 2004 i686 i686 i386 GNU/Linux
Redhat 9.
Networker server 7.1.1.
nst0 -- AIT-3
nst1 -- AIT-3
nst2 -- AIT-2
Event -- computer hung. On reboot, there was a bad block in one
of the resource files, and Networker thought there was no
jukebox defined. I redefined jukebox.
==================================================================
In my startup file, I run stinit:
# This file contains example definitions for different kinds of tape
# devices. If the user agrees with the definitions, they can be used
# in the definition file stinit.def by changing the manufacturer and
# model fields to correspond the real tape device being defined.
# The common definitions that can usually be used
# {buffer-writes read-ahead async-writes }
{buffer-writes read-ahead async-writes scsi2logical=1}
# SONY AIT-3
manufacturer="SONY" model = "SDX-700C" {
can-bsr scsi2logical drive-buffering
timeout=800
long-timeout=14400
mode1 blocksize=0 density=0x00 }
# SONY AIT-2
manufacturer="SONY" model = "SDX-500C" {
can-bsr scsi2logical drive-buffering
timeout=800
long-timeout=14400
mode1 blocksize=0 density=0x00 }
==================================================================
and in my networker startup file I have the following definitions:
NSR_DEV_BLOCK_SIZE_8MM_AIT_3=192
export NSR_DEV_BLOCK_SIZE_8MM_AIT_3
NSR_DEV_BLOCK_SIZE_8MM_AIT_2=64
export NSR_DEV_BLOCK_SIZE_8MM_AIT_2
=====================================================================
I also define the device block size in the same way in the devices
setup within nwadmin.
=====================================================================
since the reboot, when I try to mount a tape in /dev/nst0, the following
happens:
Oct 4 09:22:09 tapes logger: NetWorker media: (notice) setting (8mm
AIT-3) block size to (192 KB)
Oct 4 09:22:51 tapes kernel: st0: Block limits 2 - 16777215 bytes.
Oct 4 09:23:03 tapes kernel: st0: Incorrect block size.
Oct 4 09:23:25 tapes kernel: st0: Incorrect block size.
Oct 4 09:23:31 tapes logger: NetWorker media: (warning) /dev/nst0
reading: Success
Oct 4 09:23:45 tapes kernel: st0: Incorrect block size.
Oct 4 09:23:51 tapes logger: NetWorker media: (warning) /dev/nst0
reading: no tape label found
... and the tape is ejected.
If I do the same wih /dev/nst1, which is set the same, the mount is
successful.
I am assuming that something happened to the physical device, /dev/nst0,
which I've now disabled. But because of this previous event, I need to
make sure there is no way this could be a software/settings failure.
What's the next step.
mht
--
=============================================================
Matthew Temple Tel: 617/632-2597
Director, Research Computing Fax: 617/582-7820
Dana-Farber Cancer Institute mht AT research.dfci.harvard DOT edu
44 Binney Street, LG300/300 http://research.dfci.harvard.edu
Boston, MA 02115 Choice is the Choice!
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
|
|