Date: Tue, 24 Aug 1999 00:43:00 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Softupdates reliability? Message-ID: <199908232243.AAA55756@yedi.iaf.nl> In-Reply-To: <99Aug24.075148est.40322@border.alcanet.com.au> from Peter Jeremy at "Aug 24, 1999 7:52:41 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As Peter Jeremy wrote ... > Stephen McKay <syssgm@detir.qld.gov.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908232243.AAA55756>