Subject: Re: simultaneous use of asc0 and asc1
To: matthew green <mrg@eterna.com.au>
From: Aaron J. Grier <agrier@poofygoof.com>
List: port-alpha
Date: 02/29/2000 08:26:45
On Tue, Feb 29, 2000 at 10:12:19PM +1100, matthew green wrote:

> these are the SCSI devices connected to my 3000/400:
[SNIP]
> yes, it has 6 scsi busses. :-)  i've not experienced any problems with
> accessing the tape drive while the disks.  i do recall hearing that it
> was an *old* problem, fixed many years ago, though.

Hmm...  my setup isn't quite so large:

asc0 at tcds0 chip 0: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at asc0: 8 targets, 8 luns per target
asc1 at tcds0 chip 1: NCR53C94, 25MHz, SCSI ID 7
scsibus1 at asc1: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
probe(asc0:0:0): max sync rate 5.00Mb/s
sd0 at scsibus0 targ 0 lun 0: <DEC, RZ26     (C) DEC, T386>
	SCSI2 0/direct fixed
sd0: 1001 MB, 2570 cyl, 14 head, 57 sec, 512 bytes/sect x 2050860 sectors
cd0 at scsibus0 targ 4 lun 0: <DEC, RRD42   (C) DEC, 4.5d>
	SCSI2 5/cdrom removable
scsibus1: waiting 2 seconds for devices to settle...
probe(asc1:2:0): max sync rate 5.00Mb/s
sd1 at scsibus1 targ 2 lun 0: <CONNER, CFP1080E SUN1.05, 5150>
	SCSI2 0/direct fixed
sd1: 1030 MB, 3658 cyl, 6 head, 96 sec, 512 bytes/sect x 2110812 sectors
probe(asc1:3:0): max sync rate 5.00Mb/s
sd2 at scsibus1 targ 3 lun 0: <CONNER, CFP1080E SUN1.05, 5150>
	SCSI2 0/direct fixed
sd2: 1030 MB, 3658 cyl, 6 head, 96 sec, 512 bytes/sect x 2110812 sectors
probe(asc1:4:0): max sync rate 5.00Mb/s
sd3 at scsibus1 targ 4 lun 0: <CONNER, CFP1080E SUN1.05, 5150>
	SCSI2 0/direct fixed
sd3: 1030 MB, 3658 cyl, 6 head, 96 sec, 512 bytes/sect x 2110812 sectors
probe(asc1:5:0): max sync rate 5.00Mb/s
sd4 at scsibus1 targ 5 lun 0: <CONNER, CFP1080E SUN1.05, 5150>
	SCSI2 0/direct fixed
sd4: 1030 MB, 3658 cyl, 6 head, 96 sec, 512 bytes/sect x 2110812 sectors

/, /usr, and /var are on sd0.

I'm setting up a RAID5 on the four Conners, (thanks Greg!) but when I
initialize the parity (with 'raidctl -i'), I get a bunch of recoverable
read errors.  Poking at the internal state of the machine with a
'raidctl -s' immediately stops the read errors.  Parity also doesn't
seem to "stick" -- IE I can configure a fresh RAID, initialize the
serial number, initialize the parity, unconfigure the RAID, and when I
try and configure it again, it complains that the components aren't
clean.

I'm running a (now one day old) -current (NetBSD aragorn 1.4T NetBSD
1.4T (aragorn) #1: Mon Feb 28 22:59:59 PST 2000) .

simply creating disk activity on disks in each of the busses doesn't
seem to trigger the problem...

-- 
  Aaron J. Grier | "Not your ordinary poofy goof." | agrier@poofygoof.com
  "Time Correct function allows automatically correcting slight variation
   of your key touching manner."  --  Roland MSQ-700 manual