also sprach martin f krafft [EMAIL PROTECTED] [2007.05.06.0245 +0200]:
With the check feature of the recent md feature, the question popped
up what happens when an inconsistency is found. Does it fix it? If
so, which disk it assumes to be wrong if an inconsistency is found?
What I meant was of
martin f krafft wrote:
also sprach martin f krafft [EMAIL PROTECTED] [2007.05.06.0245 +0200]:
With the check feature of the recent md feature, the question popped
up what happens when an inconsistency is found. Does it fix it? If
so, which disk it assumes to be wrong if an inconsistency is
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
On Sun, 06 May 2007, martin f krafft wrote:
Maybe the ideal way would be to have mdadm --monitor send an email on
mismatch_count0 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
On Sunday May 6, [EMAIL PROTECTED] wrote:
On Sun, 06 May 2007, martin f krafft wrote:
Maybe the ideal way would be to have mdadm --monitor send an email on
mismatch_count0 or a cronjob that regularly sends reminders, until the
admin logs in and runs e.g. /usr/share/mdadm/repairarray.
You
Neil,
With the check feature of the recent md feature, the question popped
up what happens when an inconsistency is found. Does it fix it? If
so, which disk it assumes to be wrong if an inconsistency is found?
Cheers,
--
martin; (greetings from the heart of the sun.)
\ echo
