Date: Fri, 15 Jan 1999 10:19:34 -0600 From: Zach Heilig <zach@uffdaonline.net> To: Brian Feldman <green@unixhelp.org>, Archie Cobbs <archie@whistle.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird file corruption? Message-ID: <19990115101934.C16631@znh.org> In-Reply-To: <Pine.BSF.4.05.9901131724420.19040-100000@janus.syracuse.net>; from Brian Feldman on Wed, Jan 13, 1999 at 05:26:40PM -0500 References: <199901130527.VAA10163@bubba.whistle.com> <Pine.BSF.4.05.9901131724420.19040-100000@janus.syracuse.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 13, 1999 at 05:26:40PM -0500, Brian Feldman wrote: ... > How could it be memory when it's written to disk, extracted, then after a nearly > full build read again? Why would it extract completely the first time with no > errors? I had this exact same problem when evaluating pentium motherboards a while back. One of my (parity!) simms was marginal [later verified with a simm checker], but it was not noticed until after I made one corrupt archive [and deleted the originals]. Luckily, both the simm and the motherboard were still returnable. This also verified for me that most Intel chipsets for pentium do not use parity even if available. -- Zach Heilig <zach@uffdaonline.net> / Zach Heilig <zach@gaffaneys.com> 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?19990115101934.C16631>