home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.hardware:4108 comp.sys.sun.admin:5897
- Path: sparky!uunet!gatech!purdue!news.cs.indiana.edu!lynx!zia.aoc.nrao.edu!rmilner
- From: rmilner@zia.aoc.nrao.edu (Ruth Milner)
- Newsgroups: comp.sys.sun.hardware,comp.sys.sun.admin
- Subject: Re: Exabyte Problems with 690
- Message-ID: <1992Aug27.201257.734@zia.aoc.nrao.edu>
- Date: 27 Aug 92 20:12:57 GMT
- References: <1992Aug26.135249.28746@ibx.com> <THOMAS.TORNBLOM.92Aug26234705@beck.nexus.comm.se>
- Reply-To: rmilner@zia.aoc.nrao.edu (Ruth Milner)
- Organization: National Radio Astronomy Observatory, Socorro NM
- Lines: 24
-
- In article <THOMAS.TORNBLOM.92Aug26234705@beck.nexus.comm.se> Thomas.Tornblom@nexus.comm.se (Thomas Tornblom) writes:
- >I turned synchronous SCSI off in the kernel of our 690 about two weeks
- >ago, we haven't had a single write error on our 8500 since then. Now
- >I'm not sure if sync SCSI is the problem, at least we don't get any of
- >those silly "Blah blah target now synchronous at 3.72 M bit" messages.
-
- 8500's and DATs definitely display the problem. It is better to disable
- sync SCSI on the tape drive than on your host, especially if you have disks
- on the same SCSI bus. This can be done with 8500's (ask your vendor for a
- new firmware tape with sync SCSI disabled); unfortunately I have yet to find
- a DAT that can do it. Certainly HP and WangTek (dunno about WangDAT) can't.
-
- TTI sends their 8500's with sync SCSI already off. We got a tape from CoComp
- to do it on the ones they sold us.
-
- Sun has a "patch" which replaces esp.o, but we were told by Sun that all it
- does is suppress the "esp0: target x now synchronous ..." message. It doesn't
- prevent the renegotiation from happening as far as I know.
-
- I don't know whether this has anything to do with the original poster's poor
- performance problem with an 8500 at a specific location on the bus.
- --
- Ruth Milner NRAO/VLA Socorro NM
- Computing Division Head rmilner@zia.aoc.nrao.edu
-