All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Dorbath <light@theendofthetunnel.de>
To: Alan Piszcz <ap@solarrain.com>
Cc: xfs@oss.sgi.com
Subject: Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
Date: Sun, 06 Jul 2008 12:44:28 +0200	[thread overview]
Message-ID: <4870A20C.7080802@theendofthetunnel.de> (raw)
In-Reply-To: <alpine.DEB.1.10.0807060447180.5005@p34.internal.lan>

Justin Piszcz wrote:
> In short, utilizing Raptors (especially veliciraptors)+NCQ on the ICH8 
> w/AHCI & other cards in a RAID 5 configuration is a death trap (a good 
> way to lose your data), it appears unsafe to use NCQ w/raptors in a RAID 5
> configuration.  I've defaulted back to disabling it like I always do
> and my RAID5 is rebuilding now.

To my knowledge NCQ and Raptors is completely broken. Besides that, I 
have really bad experiences with the reliability of those drives.


-- 
Best regards,
Hannes Dorbath

  reply	other threads:[~2008-07-06 10:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.u8J+BqAcxU1mg8ob9pMBJaAHBPo@ifi.uio.no>
2008-07-05 18:38 ` Lots of con-current I/O = resets SATA link? (2.6.25.10) Robert Hancock
2008-07-05 18:54   ` Jon Nelson
2008-07-05 19:04     ` Robert Hancock
2008-07-05 22:53       ` Jon Nelson
2008-07-05 23:20         ` Robert Hancock
2008-07-05 23:50           ` Jon Nelson
2008-07-05 23:49         ` Jon Nelson
2008-07-05 19:28   ` Justin Piszcz
2008-07-05 23:22     ` Robert Hancock
2008-07-05 23:24       ` Justin Piszcz
2008-07-06 10:31         ` Justin Piszcz
2008-07-06 10:44           ` Hannes Dorbath [this message]
2008-07-06 12:13           ` Justin Piszcz
2008-07-06 12:42             ` Justin Piszcz
2008-07-06 19:51               ` Justin Piszcz
2008-07-07  9:45         ` Mattias Wadenstein
2008-07-07  9:57           ` Justin Piszcz
2008-07-07 18:14             ` Michal Soltys
2008-07-05 16:57 Justin Piszcz
2008-07-05 17:35 ` Jon Nelson
2008-07-05 17:35 ` Jon Nelson
2008-07-07 15:04 ` Gerhard Wiesinger
2008-07-07 15:08   ` Gerhard Wiesinger
2008-07-07 16:04     ` Justin Piszcz
2008-07-08  6:24       ` Gerhard Wiesinger
2008-07-08  6:59         ` Gerhard Wiesinger
2008-07-08  8:35           ` Justin Piszcz
2008-07-08 10:31             ` Gerhard Wiesinger
2008-07-08  8:34         ` Justin Piszcz
2008-07-08 10:33           ` Gerhard Wiesinger
2008-07-08 13:15             ` Justin Piszcz
2008-07-09  5:37               ` Gerhard Wiesinger
2008-07-10  1:27                 ` Henrique de Moraes Holschuh
2008-07-12  8:29                 ` Gerhard Wiesinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4870A20C.7080802@theendofthetunnel.de \
    --to=light@theendofthetunnel.de \
    --cc=ap@solarrain.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.