From owner-freebsd-hackers Wed May 30 11:45:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90]) by hub.freebsd.org (Postfix) with ESMTP id C631537B423 for ; Wed, 30 May 2001 11:45:32 -0700 (PDT) (envelope-from jandrese@mitre.org) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.9.3/8.9.3) with ESMTP id OAA13094; Wed, 30 May 2001 14:45:19 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.9.3/8.9.3) with ESMTP id OAA10132; Wed, 30 May 2001 14:45:17 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 6765719; Wed, 30 May 2001 14:45:15 -0400 Message-ID: <3B153FBC.ED53FB6C@mitre.org> Date: Wed, 30 May 2001 14:45:16 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Munish Chopra Cc: hackers@freebsd.org Subject: Re: cvsup.freebsd.org I/O error References: <20010528193755.I67783-100000@achilles.silby.com> <20010530064604.1DBFF380E@overcee.netplex.com.au> <20010530110828.L78320@numachi.com> <20010530195416.K15580@messiah.megadeb.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Munish Chopra wrote: > I just finished reading this: > > http://www.storagereview.com/jive/sr/thread.jsp?forum=1&thread=13134 > > ...it's a message board at a pretty decent storage site. There aren't > too many great posts, but what seems to be pretty consistent is that the > problems arise (in part) because Windows 98 and ME shut down too fast - > so I'm assuming this has to do with the "Yes I wrote the data (ha ha I'm > lying)" 'feature' that has been discussed lately. A few people have just > had it show up when writing to the disk... One interesting theory on there was that the drives were overheating and somehow damanging themselves. Although this doesn't seem too likely, I wonder if it isn't a catalyst. Truthfully, that board was all over the place, and I'm not sure I trust any of the posts on there any farther than I could throw them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message