linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Evans <mjevans1983@gmail.com>
To: Justin Maggard <jmaggard10@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: RAID scrubbing
Date: Fri, 9 Apr 2010 19:01:50 -0700	[thread overview]
Message-ID: <h2m4877c76c1004091901k37443583h316eb0efacbcac80@mail.gmail.com> (raw)
In-Reply-To: <s2y150c16851004091846t94347cf8u9ffd65133061d16b@mail.gmail.com>

On Fri, Apr 9, 2010 at 6:46 PM, Justin Maggard <jmaggard10@gmail.com> wrote:
> On Fri, Apr 9, 2010 at 6:41 PM, Michael Evans <mjevans1983@gmail.com> wrote:
>> On Fri, Apr 9, 2010 at 6:28 PM, Justin Maggard <jmaggard10@gmail.com> wrote:
>>> Hi all,
>>>
>>> I've got a system using two RAID5 arrays that share some physical
>>> devices, combined using LVM.  Oddly, when I "echo repair >
>>> /sys/block/md0/md/sync_action", once it finishes, it automatically
>>> starts a repair on md1 also, even though I haven't requested it.
>>> Also, if I try to stop it using "echo idle >
>>> /sys/block/md0/md/sync_action", a repair starts on md1 within a few
>>> seconds.  If I stop that md1 repair immediately, sometimes it will
>>> respawn and start doing the repair again on md1.  What should I be
>>> expecting here?  If I start a repair on one array, is it supposed to
>>> automatically go through and do it on all arrays sharing that
>>> personality?
>>>
>>> Thanks!
>>> -Justin
>>>
>>
>> Is md1 degraded with an active spare?  It might be delaying resync on
>> it until the other devices are idle.
>
> No, both arrays are redundant.  I'm just trying to do scrubbing
> (repair) on md0; no resync is going on anywhere.
>
> -Justin
>

First: Reply to all.

Second, if you insist that things are not as I suspect:

cat /proc/mdstat

mdadm -Dvvs

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

  parent reply	other threads:[~2010-04-10  2:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10  1:28 RAID scrubbing Justin Maggard
2010-04-10  1:41 ` Michael Evans
     [not found]   ` <s2y150c16851004091846t94347cf8u9ffd65133061d16b@mail.gmail.com>
2010-04-10  2:01     ` Michael Evans [this message]
2010-04-15  0:51       ` Justin Maggard
2010-04-15  1:22         ` Neil Brown
2010-04-17  0:03           ` Justin Maggard
2010-04-17  0:19             ` Berkey B Walker

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=h2m4877c76c1004091901k37443583h316eb0efacbcac80@mail.gmail.com \
    --to=mjevans1983@gmail.com \
    --cc=jmaggard10@gmail.com \
    --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).