From owner-freebsd-hackers Wed May 30 9:17:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id B77D237B424 for ; Wed, 30 May 2001 09:17:28 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 71603 invoked by uid 1000); 30 May 2001 16:17:27 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 May 2001 16:17:27 -0000 Date: Wed, 30 May 2001 11:17:27 -0500 (CDT) From: Mike Silbersack To: Brian Reichert Cc: Peter Wemm , Matt Dillon , John Polstra , Subject: Re: cvsup.freebsd.org I/O error In-Reply-To: <20010530110828.L78320@numachi.com> Message-ID: <20010530111251.R71465-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Wed, 30 May 2001, Brian Reichert wrote: > On Tue, May 29, 2001 at 11:46:04PM -0700, Peter Wemm wrote: > > Sounds like the DTLA series drives.. The biggest piles of junk I've seen!in > > quite a while. > > Could someone give me a pointer to a current discussions concerning > these drives? I've been having errant hardware problems with some > production servers, and am grasping at straws... > > -- > Brian 'you Bastard' Reichert If you do a search for "IBM DTLA failure rate" on google or deja (which would also be google, I suppose), you'll find a bunch of threads on the issue. The posts are divided into two types: 1. IBM fanboys claiming that there's a conspiracy to tarnish the DTLA's name. 2. Posts by people who say they're on their second replacement drive, and starting to see failure again. So, while it's not conclusive, it appears that there's something going on. Note that the people claiming failures say that they start as sectors going bad. Therefore, it seems entirely possible that those running their DTLAs with FAT32 won't notice a problem until they have the drive nearly full. Those with inode based FSes would probably see strange things a bit sooner. Unfortunately, I don't think you can run badblocks or anything similar right now. Maybe someone can suggest another test method. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message