Depending on your partitioning, it is most likely reconstructing the whole
15 gigs.
the cd rom should hinder your performance much.
With no out standing file system requests, raid should be reconstructing
as fast as possible. But if there is activity on the system, a command
like this may help:
echo 8192 > /proc/sys/dev/md/speed-limit
(you may want to double check that name - I don't have a linux box handy)
This is the minimum speed that raid will maintain with other activity on
the system. Use cat /proc/sys/dev/md/speed-limit to check the current
value.
Uncertain where the kernel panic may have originated. I've heard
reference to ide patches? (raid stress tests ide and scsi a great deal)
On Sun, 27 Feb 2000, Kelina wrote:
-Hey all,
-
-I'm running a new box with redhat6.1 and 2 5400rpm 15 gig harddisks.
-There's also a cd-rom drive
-on the same controller. Both the hd's are running as masters as a Raid-1
-array, and cd cd-rom as
-primary slave. While trying to get my isdn to work (i managed that now btw)
-i managed to get 2
-hard lockups and one kernel panic which complained about interrupts. This,
-Raid-1 didn't like so it
-started reconstruction, it seems to be working but it's taking *forever*.
-Now my questions are these:
-
- -Is reconstruction supposed to take over 600 minutes?
- -Does it recontruct the whole 15 gig's, or just the 3 gig of data? If so
-will i need to wait a whole
- day when my hd is full?
- -Does having the cd-rom on the same controller degrade performance, even
-tho it's not used or
- indeed even mounted?
-
-If you could answer any/all of these questions,
-
-Thx Surge
-
