Hi,
> I have an raid5 setup with an Adaptec 2940UW, 5 disks, kernel 2.2.5,
> raidtools 0.9
>
> yesterday my system crashed and after booting the system trys to reconstruct
> the raid in the background as usual in those situations.
>
> Only one thing is different: the reconstructions eats about 100K per second
> and without any limit. It takes about 4 hours until all memmory is eaten
> up an than the system crashes!! no swap is used...
I have noticed exactly the same when upgrading some 2.0.36
machines with previous (1990xxx) raid versions to 2.0.38 + the latest
(1990824) raid code, all with raid1 volumes.
I have seen this on the three machines I've upgraded (base
distribution is RH 5.2). They are very different on hardware (pentium 200,
PPro 200 and a PIII 450). All have SCSI.
As Marcus states, no swap is used. The crash comes when e2fsck'ing
automaticly the mdX while they're being reconstructed in the background...
That didn't happen with the previous releases, so watch out as it
seems to be a serious bug, I had the previous kernel installed as a
backup, and it reconstructed while e2fsck'ing without problems.
Don't hesitate on asking me to do anything it may be needed to
iron this out...
cheers,
*****---(*)---**********************************************---------->
Francisco J. Montilla System & Network administrator
[EMAIL PROTECTED] irc: pukka Seville Spain
INSFLUG (LiNUX) Coordinator: www.insflug.org - ftp.insflug.org
