Date: Wed, 25 Aug 1999 16:05:53 +1000 From: Stephen McKay <syssgm@detir.qld.gov.au> To: Wilko Bulte <wilko@yedi.iaf.nl> Cc: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy), freebsd-current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Softupdates reliability? Message-ID: <199908250605.QAA13045@nymph.detir.qld.gov.au> In-Reply-To: <199908232243.AAA55756@yedi.iaf.nl> from Wilko Bulte at "Tue, 24 Aug 1999 00:43:00 %2B0200" References: <199908232243.AAA55756@yedi.iaf.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 24th August 1999, Wilko Bulte wrote: >Hmm. I would generally expect SCSI errors etc to occur. Assuming the driver >reports those one would at least know the bus was whacko. I saw no errors, but that's not entirely surprising since I was running X11 and by that time xconsole was probably swapped out, and the disk system was stuck, so it wouldn't have been able to report anything. I gave up on a serial console a very long time ago because this machine is so reliable. :-) Also, I recall (rumour?) that the ncr driver is not as robust in the face of errors as the adaptec driver, at least with CAM. Anybody know the facts? I know, for example, that I can't get bad block lists using my scsi adapter, but people using adaptecs can. That shows that the ncr driver is in some sense incomplete. I've been meaning to look into that, but you know how time gets away. So, after all this, I still don't know if I have any real evidence of anything at all. I'll just have to keep at it until it happens again. 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?199908250605.QAA13045>