From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chet Hosey <chosey@nauticom.net>
Subject: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
Date: Tue, 31 Jan 2006 09:39:36 -0500
Message-ID: <43DF76A8.3050309@nauticom.net>
References: <E1F3vw4-0007bn-7V@www5.emo.freenet-rz.de>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <reiserfs-list-return-27962-reiserfs=m.gmane.org@namesys.com>
list-help: <mailto:reiserfs-list-help@namesys.com>
list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
list-post: <mailto:reiserfs-list@namesys.com>
Errors-To: flx@namesys.com
In-Reply-To: <E1F3vw4-0007bn-7V@www5.emo.freenet-rz.de>
List-Id: <reiserfs-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: abc1237@freenet.de
Cc: reiserfs-list@namesys.com

abc1237@freenet.de wrote:

> 	
>
>Hi,
>I don't think that this is an error of the Disc, because I have a brand new Harddisk (2 day's old).
>
>greets
>  
>

I've had new drives fail immediately. It's almost certainly not
cost-effective to fully test each drive before it leaves the factory, so
sometimes bad ones do make it through. I had a series of WD drives a few
years ago all fail within miserably within a few days to a week, for
instance.

If you're seeing I/O errors on a brand new drive, it's worth the effort
to try to have it exchanged with a different unit at the place where you
bought it.

Chet