On Thursday, Sep 9, 1999, "Thomas Seidel" writes:
>On Thu, Sep 09, 1999, [EMAIL PROTECTED] wrote:
>> On Thu, Sep 09, 1999 at 11:40:49AM +0200, [EMAIL PROTECTED] wrote:
>> > On Wed, 8 Sep 1999, Paul Jimenez wrote:
>> >
>> > > This patch is based on the md.c that shipped with the 2.2.11 kernel; it
>> > > calls md_stop() on all RAID partitions still around at shutdown/reboot
>> > > time, which allows one to have a small (non-RAID) /boot partition with
>> > > a kernel on it and a larger (RAID1) partition that's /.
>> >
>> > auto-stop has been in the newest driver for a long time. The RAID1 code in
>> > stock 2.2.11 is considered old and buggy (eg. in the case of disk failure)
>> > - it's recommended to upgrade to the newest RAID driver and do an mkraid
>> > --upgrade.
>>
>> Ingo, could you elaborate on this ?
>>
>> Are all versions of the RAID driver except for the newest one considered
>> buggy, in case of disk failure ?
>>
>> What's the problem ? Are all known problems fixed now ?
>>
>> I'm sort of wondering, because I've had a lot of luck with older versions,
>> and would hate to upgrade all the boxes if it's not necessary :)
>>
>
>I agree with you. I posted a similar patch few month ago to this list
>(ftp://ftp.ddb.de/pub/linux/root_raid1_support/). This patch is installed on
>two production servers running without any problems (kernel 2.2.9, old mdtools
>0.42, ...). The only thing I (not really) miss is an automatic reconstruction
>running in background in case of a disk failure.
You can set that up using a lilo trick if you've enough room for a spare
fs with ckraid on it someplace.
--pj
