From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265977AbUHIEqV (ORCPT ); Mon, 9 Aug 2004 00:46:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265978AbUHIEqV (ORCPT ); Mon, 9 Aug 2004 00:46:21 -0400 Received: from home.bounceswoosh.org ([66.17.169.80]:7100 "EHLO mail.bounceswoosh.org") by vger.kernel.org with ESMTP id S265977AbUHIEqU (ORCPT ); Mon, 9 Aug 2004 00:46:20 -0400 Date: Sun, 8 Aug 2004 22:48:39 -0600 From: "Eric D. Mudama" To: Jeff Garzik Cc: Alan Cox , Paul Jakma , Linux Kernel Mailing List Subject: Re: libata: dma, io error messages Message-ID: <20040809044839.GA18961@bounceswoosh.org> Mail-Followup-To: Jeff Garzik , Alan Cox , Paul Jakma , Linux Kernel Mailing List References: <1091795565.16307.14.camel@localhost.localdomain> <4113A684.8050302@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4113A684.8050302@pobox.com> User-Agent: Mutt/1.5.6+20040523i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 6 at 11:40, Jeff Garzik wrote: >libata does not (yet) retry cable errors, for example. Paul, don't >automatically assume the disk is bad, try swapping cables. In practice with large #s of drives, cable errors are a given, even with good cables... eventually *something* is going to glitch, we see it all the time in our testing, especially at elevated temperatures. --eric -- Eric D. Mudama edmudama@mail.bounceswoosh.org