From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: Software RAID (non-preempt) server blocking question. (2.6.20.4)
Date: Thu, 29 Mar 2007 04:11:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0703290410260.32099@p34.internal.lan> (raw)
In-Reply-To: <17931.23488.160031.119117@notabene.brown>
On Thu, 29 Mar 2007, Neil Brown wrote:
> On Tuesday March 27, jpiszcz@lucidpixels.com wrote:
>> I ran a check on my SW RAID devices this morning. However, when I did so,
>> I had a few lftp sessions open pulling files. After I executed the check,
>> the lftp processes entered 'D' state and I could do 'nothing' in the
>> process until the check finished. Is this normal? Should a check block
>> all I/O to the device and put the processes writing to a particular device
>> in 'D' state until it is finished?
>
> No, that shouldn't happen. The 'check' should notice any other disk
> activity and slow down if anything else is happening on the device.
>
> Did the check run to completion? And if so, did the 'lftp' start
> working normally again?
Yes it did and the lftp did start working normally again.
>
> Did you look at "cat /proc/mdstat" ?? What sort of speed was the check
> running at?
Around 44MB/s.
I do use the following optimization, perhaps a bad idea if I want other
processes to 'stay alive'?
echo "Setting minimum resync speed to 200MB/s..."
echo "This improves the resync speed from 2.1MB/s to 44MB/s"
echo 200000 > /sys/block/md0/md/sync_speed_min
echo 200000 > /sys/block/md1/md/sync_speed_min
echo 200000 > /sys/block/md2/md/sync_speed_min
echo 200000 > /sys/block/md3/md/sync_speed_min
echo 200000 > /sys/block/md4/md/sync_speed_min
>
> NeilBrown
>
next prev parent reply other threads:[~2007-03-29 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 9:59 Justin Piszcz
2007-03-29 6:25 ` Neil Brown
2007-03-29 8:11 ` Justin Piszcz [this message]
2007-03-29 8:56 ` Henrique de Moraes Holschuh
2007-03-29 9:00 ` Justin Piszcz
2007-03-30 4:38 ` Neil Brown
2007-03-30 8:12 ` Justin Piszcz
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=Pine.LNX.4.64.0703290410260.32099@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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
all inboxes | Powered by JetHome®