In regard to: Re: [Networker] Reading/writing SAIT1 tapes on Linux that...:

OK, the thing that SEEMS to solve the problem is to run "mt -f
/path/to/device status" just BEFORE the tape is loaded into the drive by
networker. What happens then is that networker can't read the drive, since
its already in use by mt. mt then returns the status as expected, and
networker ejects the tape because it couldn't read it. The interesting bit
is that when you load ANY tape after that has happened, it can read the
tape just fine! And no, this is no across-reboot persistent. :(

So, who should I talk to? The guy who wrote the QLA HBA driver? Novell?
EMC/legato? Spectralogic? My local pizza shop?

Your earlier post showed that you have an stinit.def, but are you certain
it's being used?  What does /etc/modules.conf look like on the Linux box?

Also, what does dmesg report?  Unfortunately there are no timestamps in
dmesg, so it's difficult to know what actions may have triggered any
messages that are in the ring buffer.  If you do a reboot, check dmesg,
try the read (no mt first), check dmesg, and then do the mt and the read,
that might give you a hint what's going on.

I'm just taking wild guesses here, but I'm wondering if you need

post-install st /sbin/stinit

in /etc/modules.conf, but the `mt' is triggering stinit, and that's why
you don't see the problem *after* mt has been run once.

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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
wit 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