Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266175AbUFRQfD (ORCPT ); Fri, 18 Jun 2004 12:35:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266180AbUFRQfD (ORCPT ); Fri, 18 Jun 2004 12:35:03 -0400 Received: from sweetums.bluetronic.net ([24.199.150.42]:4558 "EHLO sweetums.bluetronic.net") by vger.kernel.org with ESMTP id S266175AbUFRQeu (ORCPT ); Fri, 18 Jun 2004 12:34:50 -0400 Date: Fri, 18 Jun 2004 12:28:25 -0400 (EDT) From: Ricky Beam To: Matthias Urlichs cc: Subject: Re: SATA 3112 errors on 2.6.7 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1159 Lines: 31 On Fri, 18 Jun 2004, Matthias Urlichs wrote: >>>Current sda: sense key Medium Error > >>There's likely nothing wrong with your drives. Something about that >>driver and the hardware aren't playing nice. > >What does the drive's SMART error log report? No errors. >I would consider swapping the power supply. Last year I had *four* 120 GB >drives fail on me before I changed the thing. Zero problems since. Moral: stop buying crappy power supplies. :-) My power supply is fine. If the PS were at fault, the same thing would be happening all the time, not just when linux tries to throw 200 sectors at a time at the drives. Windows has been stressing these drives far more than linux and there's been zero idication of any problems. As I said, writing in O_DIRECT mode to the array @ _35MB/s_ never reports a DMA timeout -- I'll start increasing the buffer size to see where the cracking point is. --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/