> The first time it reports that it found (and repaired) 128 items.
> It does not mean that you now *have* 128 mismatches.
>
> The next run ('repair' or 'check') will find none (hopefully...)
> and report zero.Oh, this makes perfect sense, thanks for the explanation. As the mdadm maintainer for Debian, I would like to come up with a way to handle mismatches somewhat intelligently. I already have the check sync_action run once a month on all machines by default (can be turned on/off via debconf), and now I would like to find a good way to react when mismatch_count is non-zero. I don't want to write to the components without the admin's consent though. 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. Thoughts? 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? Thanks for your time! -martin > > -- > Eyal Lebedinsky ([EMAIL PROTECTED]) <http://samba.org/eyal/> > attach .zip as .dat > > - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
