linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jonathan Tripathy <jonnyt@abpni.co.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid Checks
Date: Sun, 3 Apr 2011 21:01:57 +1000	[thread overview]
Message-ID: <20110403210157.2c3ac83d@notabene.brown> (raw)
In-Reply-To: <4D98346F.8090502@abpni.co.uk>

On Sun, 03 Apr 2011 09:48:47 +0100 Jonathan Tripathy <jonnyt@abpni.co.uk>
wrote:

> 
> On 03/04/11 09:31, Jonathan Tripathy wrote:
> > Hi Everyone,
> >
> > I'm running CentOS 5.5 which a stock version of mdadm. I have 2 
> > physical disks in a RAID1 setup. Each disk has 4 md partitions on it.
> >
> > I'm experiencing the issues associated with the raid-check script 
> > every Sunday morning, where whatever is happening, a re-sync happens. 
> > Doing a little reading around Google, I see that this is probably 
> > caused by the mismatch_cnt being non-zero, which apparently is normal 
> > for RAID1 devices. According to this bug:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=566828
> >
> > someone has made a patch for RedHat so that mismatch_cnt isn't checked 
> > on RAID1 setups. However, since I don't use RedHat, and I don't really 
> > want to compile mdadm from scratch, is there a workaround for this? I 
> > don't want to just disable the raid-check script, as I think it does 
> > some other important checks which are useful for RAID1.
> >
> > Any help would be appreciated
> >
> > Thanks
> >
> Seems like I'm a little confused...
> 
> To apply that patch, I don't need to re-compile, as it's just a script 
> run by cron. However, looking at the script, it may not fix my "resync" 
> issue which is happening every Sunday. Looks like that script just stops 
> the mismatch warning email from being sent.
> 
> My main concern, is that during these resyncs, I loose redundancy, don't I?

No.

NeilBrown

> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2011-04-03 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03  8:31 Raid Checks Jonathan Tripathy
2011-04-03  8:48 ` Jonathan Tripathy
2011-04-03 11:01   ` NeilBrown [this message]
2011-04-03 11:04     ` Jonathan Tripathy
2011-04-03 11:19       ` NeilBrown
2011-04-03 11:30         ` Jonathan Tripathy
2011-04-03 12:18           ` John Robinson
2011-04-03 19:02             ` Jonathan Tripathy

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=20110403210157.2c3ac83d@notabene.brown \
    --to=neilb@suse.de \
    --cc=jonnyt@abpni.co.uk \
    --cc=linux-raid@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).