[Looks like I'm going to have to reply on-list]
Had similar 'Tape positioning by record is disabled.' for over a year and
couldn't get it fixed. Turned out to be a WHITESPACE problem in st.conf.
Here's what works for us on an ultra II running 2.5.1 (legacy box about to
be replaced with a 280R running Sol 9 ... someday). Because of the
sensitivity to the exact form of whitespace, and because your mail client
may gratuitiously change what I've sent, I include "od -a" output too.
# grep AIT /kernel/drv/st.conf
"SONY SDX-500C", "SONY AIT-2 tape drive", "AIT2_TAPE",
AIT2_TAPE = 1,0x36,0,0xd639,4,0x00,0x00,0x00,0x00,0;
# grep AIT /kernel/drv/st.conf | /opt/gnu/bin/od -a
0000000 ht " S O N Y sp sp sp sp S D X - 5 0
0000020 0 C " , ht " S O N Y sp A I T - 2
0000040 sp t a p e sp d r i v e " , ht " A
0000060 I T 2 _ T A P E " , nl A I T 2 _
0000100 T A P E ht = ht 1 , 0 x 3 6 , 0 ,
0000120 0 x d 6 3 9 , 4 , 0 x 0 0 , 0 x
0000140 0 0 , 0 x 0 0 , 0 x 0 0 , 0 ; nl
0000160
Fred Korz Manager, Development Support, System Management Arts
korz AT smarts DOT com 914 798 8546
On Mon, 9 Jun 2003, Oscar NOSPAM Olsson wrote:
>| I get some warnings from time to time, when it tries to do tape
>| positioning by record. It complains that the block size is 32k instead of
>| 64k. An example message below:
>|
>| Jun 9 16:39:56 britt root: NetWorker media: (notice) Volume "SL000010" on
>| device "/dev/rmt/8cbn": Cannot decode block. Verify the device
>| configuration. Tape positioning by record is disabled.
>|
>| I remember that I had some problems finding a good configuration for the
>| AIT2 drives for Solaris7 when we first installed the drives. It has been
>| an ongoing issue since then. However, since it doesn't seem to affect the
>| backup reliability, I haven't bothered looking into it before. But I am
>| curious about what could be causing this, and more important, how can it
>| be fixed? :)
>|
>| Below is an excerpt from st.conf on the backup server:
>|
>| tape-config-list=
>| "SONY SDX-500C","SONY AIT2 8mm","SONY_AIT";
>|
>| SONY_AIT = 1,0x36,0,0xd679,4,0x00,0x00,0x00,0x00,0;
>|
>| name="st" class="scsi"
>| target=0 lun=0;
>|
>| name="st" class="scsi"
>| target=1 lun=0;
>|
>| name="st" class="scsi"
>| target=2 lun=0;
>|
>| name="st" class="scsi"
>| target=3 lun=0;
>|
>| name="st" class="scsi"
>| target=4 lun=0;
>|
>| name="st" class="scsi"
>| target=5 lun=0;
>|
>| name="st" class="scsi"
>| target=6 lun=0;
>|
>| How is one supposed to REALLY know what the best definition is? I have
>| seen several suggestions for the same drives in several places. The
>| firmware on the drives themselves is fairly recent.
>|
>| One more RTFM question, the memory chip on the AIT2 tapes, how is it used
>| by networker, if at all? Does it need some kind of special configuration,
>| or is it used by default automatically?
>|
>| //Oscar
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|