On Sat, 31 May 1997 10:24:36 -0700 
 Greg Wohletz <greg@duke.CS.UNLV.EDU> wrote:

 > Actually this has happened since version 1.1.  The machine is
 > acting as an NFS server for 5 2gig seagates concatinated together
 > via the ccd driver.  Once a week or so this will happen:
 > 
 > May 30 23:27:02 bb /netbsd: sd4(bha0:5:0): timed out
 > May 30 23:27:02 bb /netbsd: sd3(bha0:3:0): timed out
 > May 30 23:27:04 bb /netbsd: sd3(bha0:3:0): timed out AGAIN

...

 > 	May 30 23:46:41 bb /netbsd: bha0: model BT-946C, firmware 4.28D
 > 
 > Anyone else see anything similar?

Not really, no... here's my configuration:

bha0 at pci0 dev 12 function 0: BusLogic 9xxC SCSI
bha0: interrupting at irq 11
bha0: model BT-958, firmware 5.05R
bha0: sync, parity
bha0 targ 0: sync, offset 15, period 100nsec
bha0 targ 1: sync, offset 15, period 100nsec
bha0 targ 8: sync, offset 15, period 100nsec
scsibus0 at bha0: 16 targets
sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST15230N, 0638> SCSI2 0/direct fixed
sd0: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec
sd1 at scsibus0 targ 1 lun 0: <SEAGATE, ST15230N, 0638> SCSI2 0/direct fixed
sd1: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec
sd2 at scsibus0 targ 8 lun 0: <SEAGATE, ST15230W, 0638> SCSI2 0/direct fixed
sd2: 4095MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sec

dracul (thorpej) ~ 174% ccdconfig -g
ccd0            64      0       /dev/sd0a /dev/sd1a

I keep several source trees on the ccd, which are accessed by 5 or 6
clients almost constantly, and the server itself does quite a bit
of building.  Objects are kept on sd2.  Basically, this machine is
my build server.

What sort of activity is going on when you see the timeout problem?

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939