home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.admin:5104 comp.sys.sun.hardware:3633
- Newsgroups: comp.sys.sun.admin,comp.sys.sun.hardware
- Path: sparky!uunet!psinntp!ptsys1!jjg
- From: jjg@pt.com (John Grana)
- Subject: Re: SCSI error messages...
- Message-ID: <1992Jul29.225022.21353@pt.com>
- Organization: Performance Technologies, Incorporated
- References: <1992Jul24.163028.16729@jyu.fi>
- Date: Wed, 29 Jul 1992 22:50:22 GMT
- Lines: 34
-
- In article <1992Jul24.163028.16729@jyu.fi> eloranta@jyu.fi (Jussi Eloranta) writes:
- >
- >Does anybody know what these error messages mean?
- >
- >Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2: transport rejected
- >Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2: transport rejected
- >Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2: kluster error- retryings ops singly
- >Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2: kluster error- retryings ops singly
- >
- >I'm using sun-4/670 with on board scsi and scsi II from pti. The drives
- >are old wrens (connected via pti scsi card). The disks seem to work ok
- >and fsck complains nothing, but there must be some purpose for these
- >messages...
- >
- >jussi
- These errors are the result of our driver (ptscII) telling the target driver
- (sd) that the requested transfer is too large... It turns out that maxphys
- appears to mean nothing to the 600mp (sun4m) kernel. BTW, the I/O still
- works because the sd driver then breaks up the I/O. Anyways, the solution
- was to compare the requested transfer size to our actual 24 bit H.W. (real)
- limit (16MB). No more "kluster errors" and, from some debug messages,
- we are doing single SCSI command transfers > 220KB! with the sun4m/sd system.
- The new driver is on its way to you.
-
- Cheers
- John Grana
- jjg@pt.com
-
-
- --
- ___________________________________________________________________________
- |John Grana, Performance Technologies Incorporated jjg@pt.com|
- |315 Science Parkway, Rochester, New York 14620 uupsi!ptsys1!jjg|
- |Phone: (716) 256-0200 Fax: (716) 256-0791 |
-