Date: Tue, 24 Aug 1999 17:59:22 +1000 From: Stephen McKay <syssgm@detir.qld.gov.au> To: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> Cc: freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Softupdates reliability? Message-ID: <199908240759.RAA14712@nymph.detir.qld.gov.au> In-Reply-To: <99Aug24.075148est.40322@border.alcanet.com.au> from Peter Jeremy at "Tue, 24 Aug 1999 07:52:41 %2B1000" References: <99Aug24.075148est.40322@border.alcanet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 24th August 1999, Peter Jeremy wrote: >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). Yes, I can't tell whether the confused SCSI adapter upset the Exabyte and maybe zero'd some disk sectors, or whether the Exabyte went bananas first and took out everything else. This system gets a LOT of use (I'm using it right now), but the Exabyte obviously isn't used as often as the disks. I might move the Exabyte on to an aha1542 as a precaution. >I'm not sure how to go about isolating the problem. I don't suppose >you happened to bump one of the cables, or suffer a power glitch? No power glitch or bumped cables. All quality gear, no overclocking, good cooling, surge suppressors, etc. I don't like "It was just one of those things". That's not how computers work. I've either got bad hardware or there are bugs. To counter the bugs, I'm about to go to the latest -stable. Bad hardware will show itself eventually. What I really should do is build a test system with softupdates and crash it a lot. (Using DDB to pause, then switch off, so no partial writes.) Could take a while... Oh, and Brian wanted to know the processor revision. I don't know of any problems with K6-2/300s, but here's the info: CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX> Stephen 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?199908240759.RAA14712>