On Sun, 06 May 2007, martin f krafft wrote: > Maybe the ideal way would be to have mdadm --monitor send an email on > mismatch_count>0 or a cronjob that regularly sends reminders, until the > admin logs in and runs e.g. /usr/share/mdadm/repairarray. > > Also, if a mismatch is found on a RAID1, how does md decide which copy is > mismatched and which is correct? What about RAID 5/6/10? I think it just picks one at random. After all, how could you reliably know which is right in a raid1 array? With raid5, I understand it just updates the parity. I had an idea to write an interactive userspace program which ran through each block on each disk device to figure out which ones didn't match up and then figure out whether it's within allocated filesystem space and if so, which file or filesystem data was affected. This would hopefully enable a user to figure out which block is wrong and correct things. Gavin - 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
