From: Jeremy Sanders <jeremy@jeremysanders.net>
To: linux-raid@vger.kernel.org
Subject: Re: stuck tasks
Date: Mon, 12 Apr 2010 14:02:21 +0100 [thread overview]
Message-ID: <hpv5kt$o52$1@dough.gmane.org> (raw)
In-Reply-To: 4BC316EC.9040808@shiftmail.org
MRK wrote:
>
> Mistake of mine, but I might have gotten the right answer by chance
> I had read resyncing but you wrote rsyncing.
> But you were in fact also resyncing from what you write below:
Not at the time of crash! Sorry for the confusion. This happened on reboot
as the drive didn't properly unmount.
> Resync speed is indeed quite low if you confirm there is no other disk
> activity.
It's not doing anything else on that drive. I think it would be faster but
the option CONFIG_MULTICORE_RAID456 was switched on in this kernel, so
there are lots of async processes fighting each other (190 of them on this
system).
> Instead if rsync is also running, you need to stop that one to have a
> proper resync speed measurement (to compute the value to be entered into
> sync_speed_max as per my previous email).
> Do you have disk write caches activated? See that with tw_cli (3ware's
> CLI) How much is /sys/block/md{n}/md/stripe_cache_size? Pump it up to
> 32768.
The disk write caches are on. The raid device is fast if you do bonnie tests
to them (>100MBs).
I tried the strip_cache_size option. The speed stays around 10 MB/s on this
system. It looks like the sync speed has slowed down a lot since the sync
started.
Jeremy
next prev parent reply other threads:[~2010-04-12 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 10:40 stuck tasks Jeremy Sanders
2010-04-12 11:06 ` MRK
2010-04-12 11:14 ` Jeremy Sanders
2010-04-12 12:49 ` MRK
2010-04-12 13:02 ` Jeremy Sanders [this message]
2010-04-12 13:38 ` MRK
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='hpv5kt$o52$1@dough.gmane.org' \
--to=jeremy@jeremysanders.net \
--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.