Date: Sun, 19 Sep 1999 22:46:58 -0700 (MST) From: John and Jennifer Reynolds <jreynold@primenet.com> To: mjacob@feral.com Subject: Re: How to tell if a quirk "worked"? Message-ID: <14309.51794.537121.179915@localhost.primenet.com> In-Reply-To: <Pine.BSF.4.05.9909192206440.43106-100000@semuta.feral.com> References: <14309.49140.814045.451806@localhost.primenet.com> <Pine.BSF.4.05.9909192206440.43106-100000@semuta.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[ On Sunday, September 19, Matthew Jacob wrote: ]
>
> Some of us don't read -questions, so that's why I haven't seen this...
Good thing I put some history of my problem in ;-)
> That one I don't know about.
it was very strange indeed ... I guess it was a "restore" message, but why I
got it, who knows.
> You can also, when the tape is loaded to BOT, do:
>
> mt -f /dev/nrsa0 seteotmodel 1
Cool. I will try that.
> printf("unable to backspace over one of double"
> " filemarks at end of tape\n");
DOH ... my grepping was flawed ... I was looking for the whole string on a
single line ....
> I now see, much to my embarrassment, that I forgot to document a "FROZEN"
> state- if the the driver thinks it has lost where things are on the tape,
> it won't let you do anything but rewind, seek to end of tape, or unload
> the tape. When any of these actions occur, normal tape operations consistent
> with that state may resume.
I should have also said I got a few of these in my syslog:
(sa0:ahc0:0:2:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state.
Tonight, I did "mt rewind" on a tape I was fooling with yesterday and got the
following in messages:
(sa0:ahc0:0:2:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x8
(sa0:ahc0:0:2:0): Queuing a BDR SCB
(sa0:ahc0:0:2:0): Bus Device Reset Message Sent
(sa0:ahc0:0:2:0): no longer in timeout, status =
anything of consequence?
>
> If you set CAMDEBUG, a quirk match will trigger this code in saregister:
>
> #ifdef CAMDEBUG
> xpt_print_path(periph->path);
> printf("found quirk entry %d\n",
> ((struct sa_quirk_entry *) match) - sa_quirk_table);
> #endif
>
> The above quirk likely should be:
>
> {
> { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "SEAGATE ",
> "STT8000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512
> },
OK. I will redo the quirk like above and include CAMDEBUG (I was actually just
reading cam(4) coincidentally :) and see if things improve. I will also do the
setoetmodel that you suggested.
>
> [ works with Ebola98 ]
> !$&!)%(&!)@(%!()@%_(!)@%)_(!@%!!!!!!!###!! :-}
*definitely*
Thanks for the response! It is quite late tonight so I'll get back to debugging
this problem tomorrow. If it is a matter of the quirk being re-written slightly
as you did above and things work, I'll send-pr with the trivial patch.
I am curious to know if anybody else reading -scsi owns or knows of somebody
who owns one of these TapeStor 8000 drives with ROM 4.11 in it? If so, are they
experiencing the same wierdness? Thanks,
-Jr
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation
jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running
jreynold@primenet.com FreeBSD 3.3-STABLE. FreeBSD: The Power to Serve.
http://www.primenet.com/~jreynold/ Come join us!!! @ http://www.FreeBSD.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14309.51794.537121.179915>