On 10/25/2009 07:33 PM, Devin Reade wrote:
...
WARNING: mismatch_cnt is not 0 on /dev/md0
I have two machines with software RAID 1 running CentOS,
they both gave this message this weekend.
Mogens
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby,
The /etc/cron.weekly/99-raid-check script is new for 5.4. Read through
the mdadm list. You will find that small mismatch counts on RAID 1 is
normal. I don't remember the exact reason but it has to do with
aborted writes where the queue has already committed the one drive and
not the other. Since
Saturday I did an upgrade from 5.3 (original install) to 5.4. Saturday
night, /etc/cron.weekly reported the following:
/etc/cron.weekly/99-raid-check:
WARNING: mismatch_cnt is not 0 on /dev/md0
md0 holds /boot and resides, mirrored, on sda1 and sdb1. md1 holds
an LVM volume
Devin Reade wrote:
Saturday I did an upgrade from 5.3 (original install) to 5.4. Saturday
night, /etc/cron.weekly reported the following:
/etc/cron.weekly/99-raid-check:
WARNING: mismatch_cnt is not 0 on /dev/md0
md0 holds /boot and resides, mirrored, on sda1 and sdb1.
On Sun, 2009-10-25 at 12:33 -0600, Devin Reade wrote:
Saturday I did an upgrade from 5.3 (original install) to 5.4. Saturday
night, /etc/cron.weekly reported the following:
/etc/cron.weekly/99-raid-check:
WARNING: mismatch_cnt is not 0 on /dev/md0
I had this happen on a
On Sun, 2009-10-25 at 14:52 -0400, Ron Loftin wrote:
On Sun, 2009-10-25 at 12:33 -0600, Devin Reade wrote:
Saturday I did an upgrade from 5.3 (original install) to 5.4. Saturday
night, /etc/cron.weekly reported the following:
/etc/cron.weekly/99-raid-check:
WARNING:
RedShift redsh...@pandora.be wrote:
What exactly is the mismatch_cnt value? If it's not too much, it is most
likely coming from your swap partition.
128. md0 is /boot only; swap is on md1 which didn't have a problem
Devin
--
A zygote is a gamete's way of producing more gametes. This may
S.Tindall tindall.sat...@brandxmail.com wrote:
mismatch_cnt (/sys/block/md*/md/mismatch_cnt) is the number of
unsynchronized blocks in the raid.
Understood.
I did the repair/check on sync_action and it got rid of the problem. (Thanks)
What I _don't_ understand is why they were
8 matches
Mail list logo