Date: Tue, 10 Nov 1998 17:09:06 +0000 (GMT) From: Mark Powell <M.S.Powell@ais.salford.ac.uk> To: freebsd-scsi@FreeBSD.ORG Subject: 3.0 scsi parity and tagged openings problems Message-ID: <Pine.BSF.3.96.981110164026.19530A-100000@plato.salford.ac.uk>
next in thread | raw e-mail | index | archive | help
Just did a fresh install of 3.0-RELEASE on a machine that previously ran
2.2.7-STABLE. It's a Viglen XX server with two 7880 chips on the
motherboard. It has three Fujitsu M2934 wide drives on each scsi bus,
connected thus:
7880 -> (da0) 2934 : (da1) 2934 : (da2) 2934 : CDROM : TAPE
7880 -> (da3) 2934 : (da4) 2934 : (da5) 2934
I have the system on da0 and want to make a ccd of drives da1 and da3.
However, when I try to newfs the newly created ccd...
# newfs /dev/rccd0a
Warning: 1280 sector(s) in last cylinder unallocated
/dev/ccd0a: 17013504 sectors in 4154 cylinders of 1 tracks, 4096
sectors
8307.4MB in 260 cyl groups (16 c/g, 32.00MB/g, 7936 i/g)
super-block backups (for fsck -b #) at:
n1, n2, n3, n4 etc.
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 125
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 125
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 124
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 124
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 122
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 122
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 121
etc. etc. until
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 64
Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 63
Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2
Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2
Then the block numbers stop. First time it happened I thought the machine
had hung, so I sshed in and rebooted it. Upon the console appeared:
syncing disks x y x ...
giving up
ahc0: data parity error detected during address or write data phase
Next time I tried it, I noticed that it hadn't actually hung, but was
still printing a block number every couple of minutes or so. I killed it
and after a few minutes got my prompt back. Then the same newfs command
worked perfectly?
Any ideas what caused that?
Cheers.
Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building
A.I.S., University of Salford, Salford, Manchester, UK.
Tel: +44 161 295 5936 Fax: +44 161 295 5888
Email: M.S.Powell@ais.salfrd.ac.uk www.pgp.com (for PGP key)
NO SPAM please: Spell salford correctly to reply to me.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981110164026.19530A-100000>