Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!ukc!dcl-cs!aber-cs!rupert!pcg From: pcg@rupert.cs.aber.ac.uk (Piercarlo Grandi) Newsgroups: comp.unix.i386 Subject: Re: ISC disk driver bug? (Was Disks Hang Under 2.0.2 SCSI add WD1006SRV2) Message-ID: Date: 19 Dec 89 20:56:39 GMT References: <654400003@cdp> <6700047@adaptex> <258C899B.28434@paris.ics.uci.edu> <258D393B.1670@paris.ics.uci.edu> <511092@nstar.UUCP> Sender: pcg@aber-cs.UUCP Organization: Coleg Prifysgol Cymru Lines: 26 In-reply-to: larry@nstar.UUCP's message of 19 Dec 89 00:18:37 GMT In article <511092@nstar.UUCP> larry@nstar.UUCP (Larry Snyder) writes: I'm no longer running the controller, like SCO - and am not having any problems. The 2372B might not be as fast - but it works. With ESIX, I get bandwidth out of the 2372B that matches that published for the WD1006. With caching disabled. BTW, the way to enable caching with the ACB is jumper J2-5, if I remember correctly. I run it disabled because it only helps really in the two following conditions: sequential reads from the block device reads from a filesystem that has been made with too small a gap which are not my type of things, and slows down more than a little on writes to the filesystem. Somebody observed that my tests have been using too large a blocking factor (on purpose, I wanted to see the maximum performance obtainable), and that read ahead may be more useful with reads using smaller block sizes. I seem to remember that I tried and this is not really true. Will do some more experiments... -- Piercarlo "Peter" Grandi | ARPA: pcg%cs.aber.ac.uk@nsfnet-relay.ac.uk Dept of CS, UCW Aberystwyth | UUCP: ...!mcvax!ukc!aber-cs!pcg Penglais, Aberystwyth SY23 3BZ, UK | INET: pcg@cs.aber.ac.uk