From: "Miro Dietiker, MD Systems" <info@md-systems.ch>
To: "'Neil Brown'" <neilb@suse.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: AW: Locking md device and system for several seconds
Date: Sun, 13 Nov 2005 12:19:20 +0100 [thread overview]
Message-ID: <018a01c5e844$18127490$4001a8c0@MDSYSPORT> (raw)
In-Reply-To: <17271.6216.944507.182685@cse.unsw.edu.au>
:-)
>Can you check which IO scheduler the drives are using, try different
>schedulers, and see if it makes a different.
there was [anticipatory] selected.
ORIGINAL:
tiger:~# grep . /sys/block/*/queue/scheduler
/sys/block/fd0/queue/scheduler:noop [anticipatory] deadline cfq
/sys/block/hdd/queue/scheduler:noop [anticipatory] deadline cfq
/sys/block/sda/queue/scheduler:noop [anticipatory] deadline cfq
/sys/block/sdb/queue/scheduler:noop [anticipatory] deadline cfq
NEW:
tiger:~# grep . /sys/block/*/queue/scheduler
/sys/block/fd0/queue/scheduler:noop anticipatory deadline [cfq]
/sys/block/hdd/queue/scheduler:noop anticipatory deadline [cfq]
/sys/block/sda/queue/scheduler:noop anticipatory deadline [cfq]
/sys/block/sdb/queue/scheduler:noop anticipatory deadline [cfq]
System seems to work, but I need some testing time to check that
behaviour. (Any suggestion of a testing tool to generate disk
traffic and reporting response-times and throughput?)
Which is the right way / position on bootup to set this field
permanent to this value and what exactly did I change with this
modification? (Performance issues?)
I'm using debian..
I also need to check this on the other (identical) machines.
Thanks! Miro Dietiker
-----Ursprüngliche Nachricht-----
Von: Neil Brown [mailto:neilb@suse.de]
Gesendet: Sonntag, 13. November 2005 11:41
An: Miro Dietiker, MD Systems
Cc: linux-kernel@vger.kernel.org
Betreff: Re: Locking md device and system for several seconds
On Sunday November 13, info@md-systems.ch wrote:
> Hi!
>
> I'm using kernel 2.6.14.2 with md (RAID1 static) as bootable.
>
> While md synching (initial creation or after marked one as failed,
> removed and re-added) there are some locking problems with the
> complete system/kernel.
Can you check which IO scheduler the drives are using, try different
schedulers, and see if it makes a different.
grep . /sys/block/*/queue/scheduler
will show you (the one in [brackets] is active).
Then just echo a new value out to each file.
I've had one report that [anticipatory] causes this problem and [cfq]
removes it. Could you confirm that?
Thanks,
NeilBrown
next prev parent reply other threads:[~2005-11-13 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 10:31 Miro Dietiker, MD Systems
2005-11-13 10:41 ` Neil Brown
2005-11-13 11:19 ` Miro Dietiker, MD Systems [this message]
2005-11-13 11:58 ` AW: " Philippe Pegon
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='018a01c5e844$18127490$4001a8c0@MDSYSPORT' \
--to=info@md-systems.ch \
--cc=linux-kernel@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®