mismatch_cnt != 0, member content mismatch, but md says the mirror is good

[Ben Scott]

On Thu, Nov 19, 2009 at 5:48 PM, Michael ODonnell
<michael.odonnell at comcast.net> wrote:
> ...with a plausible (and somewhat comforting) nuts&bolts level explanation toward
> the bottom of the latter.  Summary: annoying but apparently not harmful.

  As I understand it, the explanation in question applies to swap
partitions only.  (Swap is somewhat unique in that the kernel can
"know" a given block on disk will never be read again.)

  For <liberty.gnhlug.org>, the partition in question is an EXT3
filesystem.  Interestingly enough, the LVM PV which contains an LV
with swap on it is not reporting a non-zero mismatch_cnt (yet).

-- Ben