Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Nov 1996 18:41:16 +0300 (MSK)
From:      "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" (Andrey A. Chernov) <ache@nagual.ru>
To:        gibbs@freefall.freebsd.org (Justin T. Gibbs)
Cc:        current@freebsd.org, scsi@freebsd.org
Subject:   Re: SCB paging is most dangerous option now!
Message-ID:  <199611121541.SAA00746@nagual.ru>
In-Reply-To: <199611120703.XAA27655@freefall.freebsd.org> from "Justin T. Gibbs" at "Nov 11, 96 11:03:56 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> What were the error messages?
> 

They not stored anywhere now because it seems ANY disk write cause
immediately destruction of inode table including syslog writes.
As I remember there was something like:

data overrun of XXXX bytes detected

followed by various retraining/resetting failure attempts.
As I remember no one successfull write's happens.

my configuration:
ahc0: <Adaptec 284X SCSI host adapter> at 0x1c00-0x1cff irq 11 on eisa0 slot 1
ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs

when SCB paging is enabled, this line looks like
ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4/255 SCBs

ahc0: target 0 Tagged Queuing Device
(ahc0:0:0): "CONNER CFP1060S 1.05GB 213C" type 0 fixed SCSI 2
				    ^^^^ upgraded
sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors)
ahc0: target 1 Tagged Queuing Device
(ahc0:1:0): "IBM DORS-32160 S84A" type 0 fixed SCSI 2
sd1(ahc0:1:0): Direct-Access 2063MB (4226725 512 byte sectors)

As I already say, SCB paging works with any _one_ device alone.

-- 
Andrey A. Chernov
<ache@nagual.ru>
http://www.nagual.ru/~ache/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611121541.SAA00746>