Thanks! I did have to remove a tape from the SDLT P1000 the other day,
and I did not want to have to replace it with another tape so I tried
the withdraw command using nsrjb and it did work without locking the
load port door, BUT I did not try depositing anything so maybe the
problem occurs if you're depositing tapes. Seems that when I was doing
my testing I was depositing and withdrawing and not just one or the
other exclusively.

George

Jose Quinteiro wrote:
>
> Hello George,
>
> That message appears in newer versions of the Linux st driver.  It's
> present in version 20030406 but not in version 20020805 (which is used
> by the stock 2.4.20 kernel.)
>
> These messages are benign. They will be printed whenever we verify the
> label of a tape that's been rewound all the way to the beginning. You
> can turn them off in syslog.conf if they're annoying you.
>
> I haven't forgotten about your P1000 problem - I just haven't had a
> chance to work on it.
>
> Saludos,
> Jose.
>
> George Sinclair wrote:
> > Hi,
> >
> > We're seeing the following type of message(s) in our /var/log/messages
> > file on our storage node server:
> >
> > Jun 10 13:54:24 hostname kernel: st0: Failed to read 131072 byte block
> > with 32768 byte read.
> > Jun 17 01:55:21 hostname kernel: st5: Failed to read 65536 byte block
> > with 32768 byte read.
> >
> > These have been showing up pretty much daily as far back as the logs go
> > -- at least since mid to late May 2003. The ones for st0 and 1 show up
> > with the 131072 byte and the ones for st2, 3, 4 and 5 show up with the
> > 65536. Often they are intermixed. We're running two libraries on this
> > Linux RedHat storage node server: One is a Quantum SDLT P1000 with two
> > SDLT drives (st0, st1) and the other is a Storagetek L80 with 4 LTO
> > drives (st2, 3, 4 and 5). We are having no problems with backups or
> > recoveries (actually, sometime back we we're seeing those "positioning
> > by record disabled" messages during recoveries, and that's when we
> > created the stinit.def file. We did not have one prior. This fixed that
> > problem and recoveries then worked like a champ. We've had no problems
> > since.) and we DO have an /etc/stinit.def file (see below). We are
> > running 6.1.1 on both the primary server (Solaris 8) and the storage
> > node (Linux Redhat 7.3).
> >
> > The following is from a 'uname -a' on the storage node:
> >
> > Linux hostname 2.4.20-13.7smp #1 SMP Mon May 12 12:31:27 EDT 2003 i686
> > unknown
> >
> > I have considered upgrading to 6.1.3 (the last stable release prior to
> > 7.0, or so I thought), but I've heard about some problems and didn't
> > want to rock the boat since everything seems to be running smoothly
> > under 6.1.1.
> >
> > Would appreciate any help on this.
> >
> > Thanks.
> >
> > George
> > George.Sinclair AT noaa DOT gov
> >
> >
> > Here's a copy of the stinit.def file:
> >
> > # Seagate Ultrium LTO
> > manufacturer=SEAGATE model = "ULTRIUM06242-XXX" {
> > scsi2logical=1 can-bsr auto-lock
> > mode1 blocksize=0
> > }
> >
> > # SDLT220
> > manufacturer="QUANTUM" model = "SuperDLT1" {
> > scsi2logical=1
> > can-bsr=1
> > auto-lock=0
> > two-fms=0
> > drive-buffering=1
> > buffer-writes
> > read-ahead=1
> > async-writes=1
> > can-partitions=0
> > fast-mteom=1
> > #
> > # If your stinit supports the timeouts:
> > timeout=3600 # 1 hour
> > long-timeout=14400 # 4 hours
> > #
> > mode1 blocksize=0 density=0x48 compression=1    # 110 GB + compression
> > mode2 blocksize=0 density=0x48 compression=0    # 110 GB, no compression
> > }
> >
> > We also have the following line at near the end of /etc/modules.conf:
> >
> > post-install st /sbin/stinit
> >
> > --
> > 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.
> > =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=