But anyway, it's better, so thank you! I haven't rebooted the celeron
I hung for the duration of a RAID-1 check, so I haven't checked that with
2.6.18 yet.
Followup: 2.6.18 installed and tested; no change. The machine still
goes away for the duration if three RAID-1 checks are run in
Just to follow up my speed observations last month on a 6x SATA - 3x
PCIe - AMD64 system, as of 2.6.18 final, RAID-10 checking is running
at a reasonable ~156 MB/s (which I presume means 312 MB/s of reads),
and raid5 is better than the 23 MB/s I complained about earlier, but
still a bit
Hi Bill,
On Mon, 04 Sep 2006 12:42:53 -0400
Bill Davidsen [EMAIL PROTECTED] wrote:
Mark Smith wrote:
Interesting, but do you run other stuff at that time? Several
distributions run various things in the middle of the night which really
bog the machine.
Doesn't look like it.
Mark Smith wrote:
Just a note, I've noticed this problem too. I run a RAID1 check once
every 24 hours, and while developing the script to do it, noticed that
the machine became virtually unusable - mouse was jumpy, typing lagged.
I run this check every morning at 4.00am so I'm usually
[EMAIL PROTECTED] wrote:
I don't think the processor is saturating. I've seen reports of this
sort of thing before and until recently had no idea what was happening,
couldn't reproduce it, and couldn't think of any more useful data to
collect.
Well I can reproduce it easily enough.
I'd like to note that the symptoms include not even being
able to *type* at the console, which I thought was all in-kernel
code, not subject to being swapped out. But whatever.
Really? Or is it just that you can type but the characters don't get
echoed. The type part is in the kernel, but
Hi Bill,
On Mon, 04 Sep 2006 12:42:53 -0400
Bill Davidsen [EMAIL PROTECTED] wrote:
Mark Smith wrote:
Just a note, I've noticed this problem too. I run a RAID1 check once
every 24 hours, and while developing the script to do it, noticed that
the machine became virtually unusable -
Just a note, I've noticed this problem too. I run a RAID1 check once
every 24 hours, and while developing the script to do it, noticed that
the machine became virtually unusable - mouse was jumpy, typing lagged.
I run this check every morning at 4.00am so I'm usually asleep and
don't notice it,
The PCI bus is only capable of 133MB/s max. Unless you have dedicated
SATA ports, each on its own PCI-e bus, you will not get speeds in excess
of 133MB/s, 200MB/s+ I have read reports of someone using 4-5 SATA
controllers (SiI 3112 cards on PCI-e x1 ports) and they got around 200MB/s
or
I don't think the processor is saturating. I've seen reports of this
sort of thing before and until recently had no idea what was happening,
couldn't reproduce it, and couldn't think of any more useful data to
collect.
Well I can reproduce it easily enough. It's a production server, but
I
Two discoveries: first, I locked up my machine, and second, it's surprisingly
slow.
I think the former is pilot error, and not a bug, but after applying
the raid-1 check patch (cherry-picked from the v2.6.18-rc4-mm3 tree at
git://git.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git)
to a
Second, trying checks on a fast (2.2 GHz AMD64) machine, I'm surprised
at how slow it is:
The PCI bus is only capable of 133MB/s max. Unless you have dedicated
SATA ports, each on its own PCI-e bus, you will not get speeds in excess
of 133MB/s, 200MB/s+ I have read reports of someone using
12 matches
Mail list logo
