you could write a simple shell or perl script to do this using the
/proc/mdstat as a reference, but it is a bad idea to put in a drive and have
the kernel _assume_ you want to put things back the way they were. i prefer
the control, rather than have the kernel assume.
allan
Emmanuel Galanos <[EMAIL PROTECTED]> said:
> Greetings,
> If this is documented somewhere feel free to tell me where it is:
>
> I just setup a software RAID 1 using 2 IDE disks and no spares. I'm
> using the kernel that comes with the RH beta (md 0.90.0, raidtools 0.90).
>
> Anyway to test it, I halted the machine then disconnected one of the
> drives. Booted the machine, it goes into degraded mode. Everything fine.
> Power down. Reconnect drive. Restart. The array still stays in degraded mode
:(
> (timecounter was out by 2).
>
> Looking at the source this is the intended behaviour if the md devices
> are out of sync by more than one time increment. I managed to then find the
> command raidhotadd, and was thus able to add the extra partitions back into
> the array (I am using 5 md devices) manually, and everything was peachy
again.
> Only problem was that it was ugly having to specify each of the
> individual partitions/md devices.
>
> Question: Without having spare disks is there a way to get md to
> automatically start a reconstruction using the "freshest" copy? (besides
> getting rid of the test in the source). Is there a reason why it should not
> do this?
>
> Thanks.
> emmanuel
>
--
