On Monday May 21, dondster@xxxxxxxxx wrote: > On 5/16/07, Don Dupuis <dondster@xxxxxxxxx> wrote: > > > > I am still trying to get where I had the low recover rate with the > > bitmap turned on. I will get back with you > > Don > > > Any new updates Neil? > Any new things to try to get you additional info? > THanks > > Don You said "I will get back with you" and I was waiting for that... I hoped that your further testing might reveal some details that would shine a light on the situation. One question: Your description seems to say that you get corruption after the resync has finished. Is the corruption there before the resync starts? I guess what I would like it: Start with fully active array. Check for corruption. Remove one drive. Check for corruptions. Turn off system. Turn it on again, array assembles with one missing device. Check for corruption. Add device, resync starts. Check for corruption. Wait for resync to finish. Check for corruption. NeilBrown - 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
