The recovery daemon adjusts reconstruction speed dynamically according to
available system resources.
Disk I/O is somewhat slower but works just fine. You don't have to wait.
Hervé Eychenne wrote:
Hi,
Suppose I'm waiting for a recovery to be completed, and want to run a
command afterwards
peter pilsl wrote:
The only explantion to me is, that I had the wrong entry in my
lilo.conf. I had root=/dev/hda6 there instead of root=/dev/md2
So maybe root was always mounted as /dev/hda6 and never as /dev/md2,
which was started, but never had any data written to it. Is this a
possible
Generally the min/max values make no difference as long as max is 45000.
System use during resync is the biggest factor other than raw CPU.
Check actual resync times:
cat /var/log/messages.8 | synctime
array, blocks, sec, blocks/s, start, finish
md10,2104448,63, 33403.9, Mar 16
1. Grab coreutils 5.2.1 from gnu.org and the debian patch from
http://packages.debian.org/unstable/base/coreutils
2. Extract the 2 dd patches which start with the line
+--- coreutils-5.0/src/dd.c.orig2003-02-07 07:39:20.0 -0500
through, but not including, the line
---
Gordon Henderson wrote:
Anyone using Tyan Thunder K8W motherboards???
I now know, there is a K8S (server?) version of that mobo, but at the time
it was all orderd, I wasn't aware of it - my thoughts are there there is
some sort of PCI/PCI-X problem with either the motherboard or the chipset,
and
Gordon Henderson wrote:
What I wanted was an 8-way RAID-1 for the boot partition (all of /, in
reality) and I've done this many times in the past on other 2-5 way
systems without issue. So I do the stuff I've done in the past, and theres
nothing really new to me in that respect. (I'm using LILO)
Gordon Henderson wrote:
...
It seemed more stable with just one PCI card in, so I have a 4-port card
on order as a last ditch attempt to make it work - I did try re-flashing
the BIOS on one board, (I have 2) as it seemed to be about a year old and
there are several updates on the Tyan web-site,
I have two disks as raid on a BP6 (HPT366) and had one too many
lockups on hde+hdg, so I decided to move it down to hdb+hdd.
I've fixed two BP6s (V1.0 and V1.1) using the EC10 cap upgrade method.
More detail is available on several of the Abit-centric overclocker
sites.
Between the two PGA
