I've had this problem. I turned the raid speed limit max to 0, slept for a second (just because), did my hdparm commands, slept another second (again, just because - may not be necessary), then turned the raid speed limit back to something that was good for background reconstruction. That got rid of my dropped interrupts -Mike danci@xxxxxxxxx wrote: > On Wed, 25 May 2005, Catalin(ux aka Dino) BOIE wrote: > > >>>So I need to know if there is any way (kernel parameter would be >>>ideal) to delay reconstruction for X seconds/minutes? >>> >>>Any other suggestions to deal with the problem? >> >>You can hot-remove the previous failed disk (anyway, it just started to >>resync). Then, activate DMA, then hot-add the disk to array. >> >>Hope it helps. > > > Thanks for the suggestion - this may be the last resort (I'd like to keep > the init-scripts as clean as possible). > > I forgot to mention that I'm using 2.4 kernels (2.4.27 at the moment, > 2.4.30 on the test machine - but it does the same thing). > > There is a module 'piix.o' that needs to be loaded before I can use DMA at > all. It's loaded via init scripts - I will try putting it in the initrd. > > D. > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
