From: Gerhard Wiesinger <lists@wiesinger.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
Date: Tue, 8 Jul 2008 08:24:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.1.10.0807080811560.5439@bbs.intern> (raw)
In-Reply-To: <alpine.DEB.1.10.0807071149530.32508@p34.internal.lan>
On Mon, 7 Jul 2008, Justin Piszcz wrote:
> Hi Gerhard,
>
> It /could/ be the port itself if you have changed the cable and disk..
>
Yes, but it is very unlikely. I have written TB of data there without any
problems. Anyway this is my 3rd exchanged SAMSUNG disk ...
> Have you tried loading the disk with dd and seeing if you can reproduce the
> problem? You are getting the same error I get generally, I can recommend
> turning OFF NCQ first and see if the problem goes away.
>
> # Define DISKS.
> cd /sys/block
> DISKS=$(/bin/ls -1d sd[a-z])
>
> # Disable NCQ on all disks.
> echo "Disabling NCQ on all disks..."
> for i in $DISKS
> do
> echo "Disabling NCQ on $i"
> echo 1 > /sys/block/"$i"/device/queue_depth
> done
>
I tried to disable NCQ on all disks and tried to rebuild the raid, but it
still failed to rebuild with the same error message.
I also tried the nolapic kernel parameter without success.
/dev/sda: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
/dev/sdb: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
/dev/sdc: 5 Reallocated_Sector_Ct 0x0033 091 091 010 Pre-fail Always - 413
/dev/sdd: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
/dev/sde: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
/dev/sdf: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
The only thing is that the Reallocated_Sector_Ct is still >0 on /dev/sdc
(keep in mind this is my 3rd new Samsung disk on /dev/sdc and I had up to
3000 Reallocated_Sector_Ct on previous disks in < 1 day !!!).
Should I replace the disk a fourth time?
When you search in google you find a lot of threads with the timeout
problem. Might this be a software issue?
Any ideas?
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
next prev parent reply other threads:[~2008-07-08 6:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 16:57 Lots of con-current I/O = resets SATA link? (2.6.25.10) 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 [this message]
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
[not found] <fa.u8J+BqAcxU1mg8ob9pMBJaAHBPo@ifi.uio.no>
2008-07-05 18:38 ` 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
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
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=alpine.LFD.1.10.0807080811560.5439@bbs.intern \
--to=lists@wiesinger.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/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.