RE: mismatch_cnt of 128 and 1408.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



} -----Original Message-----
} From: linux-raid-owner@xxxxxxxxxxxxxxx [mailto:linux-raid-
} owner@xxxxxxxxxxxxxxx] On Behalf Of Neil Brown
} Sent: Monday, March 24, 2008 11:34 PM
} To: Janek Kozicki
} Cc: linux-raid@xxxxxxxxxxxxxxx
} Subject: Re: mismatch_cnt of 128 and 1408.
} 
} On Monday March 24, janek_listy@xxxxx wrote:
} >
} > 5. then after reboot: /usr/share/mdadm/checkarray -a ; cat
} /sys/block/md?/md/mismatch_cnt
} >    md0: 128
} >    md1: 0
} >    md2: 1408
} >
} > Now I am alarmed that something might be wrong with the root
} > partition. From other posts I remember that mismatch count for swap
} > partitions is allowed to be nonzero.
} 
} Yes, the 'swap' is nothing to worry about.

How can a mismatch on swap be ok?  Seems the wrong data could be read in 50%
of the time.

Thanks,
Guy

} 
} As md does it's checks in units of around 128 sectors, the "md0: 128"
} probably just means a single sector is different between the two.
} 
} I recommend
} 
}   echo repair > /sys/block/md0/md/sync_action
} 
} That will fix it.
} 
} Probably just another 'fsck -f' after that just to be on the same
} side.
} 
} NeilBrown
} --
} 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

--
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux