:-)
>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:[email protected]]
Gesendet: Sonntag, 13. November 2005 11:41
An: Miro Dietiker, MD Systems
Cc: [email protected]
Betreff: Re: Locking md device and system for several seconds
On Sunday November 13, [email protected] 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
