On Tuesday December 6, djani22@xxxxxxxxxxxxx wrote: > Hello, list, > > > Is there a way to force the raid to skip this type of resync? Why would you want to? The array is 'unclean', presumably due to a system crash. The parity isn't certain to be correct so your data isn't safe against a device failure. You *want* this resync. If you are using 2.6.14 to later you can try turning on the write-intent bitmap (mdadm --grow /dev/md0 --bitmap=internal). That may impact write performance a bit (reports on how much would be appreciated) but will make this resync-after-crash much faster. NeilBrown > > Every 2s: cat /proc/mdstat Tue Dec 6 01:28:55 > 2005 > > Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] > [raid10] [f > aulty] > md0 : active raid5 sdb1[4] sda1[10] hds1[5] hdq1[2] hdo1[3] hdm1[8] hdk1[6] > hdi1 > [7] hde1[9] hdc1[1] hda1[0] > 1953583360 blocks level 5, 32k chunk, algorithm 2 [11/11] > [UUUUUUUUUUU] > [=>...................] resync = 6.0% (11758724/195358336) > finish=1216.8 > min speed=2512K/sec - 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
