Re: performance limitations of linux raid

[=3D=3FISO-8859-2=3FQ=3FJure=5FPe=E8ar=3F=3D]

> In the last 24 hours ive been getting them when e2fsck runs after
> rebooting. Usual cause of rebooting is irq causeing lockup, or endlessly
> trying looping trying to get an irq.
> 
> Im convinced its my hpt366 controller, ive mentioned my problem in a few
> channels, no luck yet.
> 
> I used to think it was the raid code, but i get it with lvm as well, it
> happens more often from reading than writting via the HPT366, the more
> load placed on the controller the more likely it is to lockup, one drive
> by itself it just losses interrupts (sometimes it can recover), if use
> three or four channels, using both my onboard hpt366 and my pci card it
> locks up hard in a fraction of a second
> 
> I want to try and work this problem out, im not a kernel hacker though.

me too ... have the same problem over here with hpt366 (abit 
hotrod) and 4 ibm 25gb disks. i thought this happens when array 
i/o is high, but recently seen some (with successfull recovery) 
when disks were quiet. i guess we really need some expert kernel 
hacker to sort this out...

btw, i'm new to this list and have some (already answered i guess) 
questions. what's the current status of linux raid? 2.2 patch seems 
to be stuck at .11. is there any general recipie to make it work in 
recen kernels? i need to have it working in 2.2.15pre19 with ide 
patch also. please enlighten me :) 

|Pegasus|