All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Steven Ellis <steven@openmedia.co.nz>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Can't resolve mismatch_count > 0 for a raid 1 array
Date: Wed, 08 Apr 2009 17:50:46 -0400	[thread overview]
Message-ID: <49DD1C36.1000306@tmr.com> (raw)
In-Reply-To: <F87E9034-BDD7-4D74-8117-3ED1884D4165@openmedia.co.nz>

Steven Ellis wrote:
> I've resolved most of my raid issues by re-housing the affected system 
> and replacing the motherboard, but across the 3 boards I've tried I 
> always have an issue with my /dev/md1 array producing mismatch_count 
> of 128 or 256.
>
> System is running Centos 5.2 with a Xen Dom0 kernel
>
> This md1 volume is a pair of 40GB HDs raid1 on an IDE controller which 
> I them have a bunch of LVM's that are my Xen guests.
>
> Is there any chance that these mismatch_count values are due to swap 
> partitions for the Xen guests?

That's the cause, and since md code doesn't currently have a clue which 
copy is "right" it's always a problem if you do something like suspend 
to disk. You probably don't do that with xen images, but swap and raid1 
almost always have a mismatch.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc

"You are disgraced professional losers. And by the way, give us our money back."
    - Representative Earl Pomeroy,  Democrat of North Dakota
on the A.I.G. executives who were paid bonuses  after a federal bailout.



  parent reply	other threads:[~2009-04-08 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 10:03 Can't resolve mismatch_count > 0 for a raid 1 array Steven Ellis
2009-04-08 21:49 ` Goswin von Brederlow
2009-04-09  0:07   ` Steven Ellis
2009-04-08 21:50 ` Bill Davidsen [this message]
2009-04-08 22:00   ` Iustin Pop
2009-04-09  0:13     ` Steven Ellis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49DD1C36.1000306@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=steven@openmedia.co.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.