From owner-freebsd-current Tue Aug 24 3: 8:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A52861504E for ; Tue, 24 Aug 1999 03:08:25 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id MAA26393; Tue, 24 Aug 1999 12:00:11 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA55756; Tue, 24 Aug 1999 00:43:00 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908232243.AAA55756@yedi.iaf.nl> Subject: Re: Softupdates reliability? In-Reply-To: <99Aug24.075148est.40322@border.alcanet.com.au> from Peter Jeremy at "Aug 24, 1999 7:52:41 am" To: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) Date: Tue, 24 Aug 1999 00:43:00 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Peter Jeremy wrote ... > Stephen McKay wrote: > >I was extracting from the Exabyte to the DDRS disk while applying a CTM > >update from that disk against one of the DCAS disks when it crashed. The > >Exabyte went wonky (took about 6 goes to get the tape ejected) and the > >rest of the disk system locked up. The SCSI adapter was so confused I > >had to power down. > > The exact order of events is not clear from this. In general, I'd say > that if something managed to upset the SCSI bus sufficiently to > confuse every target on it, then there's a reasonably likelihood that > data transfers were also corrupted. A serious bus corruption during a > disk write (either command or data phase) would have a reasonable > chance of resulting in corrupt data on the disk (either the wrong data > in the right place or the right data in the wrong place). Hmm. I would generally expect SCSI errors etc to occur. Assuming the driver reports those one would at least know the bus was whacko. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message