From: Asdo <asdo@shiftmail.org>
To: "Kristleifur Daðason" <kristleifur@gmail.com>,
"Timothy D. Lenz" <tlenz@vorgon.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: possible bus loading problem during resync
Date: Tue, 09 Mar 2010 12:00:17 +0100 [thread overview]
Message-ID: <4B962A41.50207@shiftmail.org> (raw)
In-Reply-To: <73e903671003090230y135d104cte15e07604b85b8aa@mail.gmail.com>
Kristleifur Daðason wrote:
> On Tue, Mar 9, 2010 at 6:31 AM, Timothy D. Lenz <tlenz@vorgon.com> wrote:
>
>> I'm working on 2 systems that are mainly for running vdr. I've had these
>> running somewhat for awhile with raid. But a couple nights ago as I was
>> quitting for the night, I noticed one of the computers drive light staying
>> on. I had just made some changes to xine and didn't know if something had
>> crashed. Turned on the TV and found the video was freezing for 10-20secs
>> every 10-20secs. Logging in using putty and winscp I found it very sluggish
>> to respond.Starting top I found it was doing the regular array check/resync.......
>> --
>>
>
>
> Sorry about the incredibly brief answer: Not to dismiss other issues,
> but that behavior seems like exactly what I've seen when a disk has
> been failing.
>
If that is true, how does that happen, the driver is hung? But anyway,
how can such things happen when there is more than one CPU-core?
try disabling NCQ by echo 1 > /sys/block/sdX/device/queue_depth for all
drives. After doing this, at most 1 request can be issued to one drive
until the drive has serviced such request.
After doing this, firstly I'd say the sluggishness should disappear, at
least on SSH when not touching the disks. And then you can look with
"iostat -x 1": probably the bad drive will have a service time (svctm)
or await much worse than the others.
Just guesses, correct me if I'm wrong
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-09 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 6:31 possible bus loading problem during resync Timothy D. Lenz
2010-03-09 10:30 ` Kristleifur Daðason
2010-03-09 11:00 ` Asdo [this message]
2010-03-11 5:53 ` Goswin von Brederlow
2010-03-12 11:00 ` Asdo
2010-03-12 11:43 ` Kristleifur Daðason
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=4B962A41.50207@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=kristleifur@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=tlenz@vorgon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).