All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-raid@vger.kernel.org
Subject: possible bus loading problem during resync
Date: Mon, 08 Mar 2010 23:31:58 -0700	[thread overview]
Message-ID: <4B95EB5E.5090702@vorgon.com> (raw)

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. The process was using about 64% cpu and cpu 
was staying at idle speed (1000Mhz). These computers use Athlon64 x2 
cpu's. A problem with the AN2 socket systems is that when the cpu is 
throttled back, it also slows the bus. This has been found to be a 
problem on boards with integrated graphics when using nvidia's vdpau for 
hardware video decoding because they use system ram. The fix is to set 
the lower speed limit to 1800Mhz and/or change the up_threshold to ~50% 
. However, I am using PCIe video cards and so up till now have not had a 
problem.

I stopped vdr, but putty and winscp where still sluggish. This tells me 
that it is loading the bus so much that both the video card and the 
network is effected. it would also effect any tuner cards interfering 
with any recording that may be going on at the time. I change the 
up_threshold from the default 95% to 50% which should kick the speed up 
when it's syncing. But I'm not sure that will be enough. Could there be 
some other setting that is wrong raising the priority of the process? 
Seems like this would be a problem for any system having raid 
maintenance bring the system to its knees. The eta to finish was 75 minutes.

             reply	other threads:[~2010-03-09  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09  6:31 Timothy D. Lenz [this message]
2010-03-09 10:30 ` possible bus loading problem during resync Kristleifur Daðason
2010-03-09 11:00   ` Asdo
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=4B95EB5E.5090702@vorgon.com \
    --to=tlenz@vorgon.com \
    --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.