martin f krafft wrote:
That sounds right. Some arrarys have persistent mismatches if they are in use, you are unlikely to want to even attempt to take corrective action. You might want to have a config file and just run a program which reads the config regularly and acts based on what it finds.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.
-- bill davidsen <davidsen@xxxxxxx> CTO TMR Associates, Inc Doing interesting things with small computers since 1979 - 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
