public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "Majed B." <majedb@gmail.com>
To: Linux Raid Study <linuxraid.study@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid5 Read stats for parity cal...
Date: Thu, 17 Sep 2009 03:20:19 +0300	[thread overview]
Message-ID: <70ed7c3e0909161720r5a068ca4m8335cfbbd51bc220@mail.gmail.com> (raw)
In-Reply-To: <f5d1f90a0909161713s2f31e3b4t34a4ee285b83ef8e@mail.gmail.com>

You can force an array check by writing "check" (without double
quotes) to a file named "sync_action" found in /proc/sys

Read this for further details: http://linux.die.net/man/4/md

You can run that check at any time, not just when there's a problem.

On Thu, Sep 17, 2009 at 3:13 AM, Linux Raid Study
<linuxraid.study@gmail.com> wrote:
> Hello:
>
> I understand that parity calculations are not done as part of Raid5
> read operation in normal running conditions.
>
> However, it would be done during disk failure or when a sector is bad.
> Is there a way (any stats) available to see if parity cal are done
> when sector is bad (since this is not as obvious as a disk fail...)
>
> Thanks!
> --
> 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
>



-- 
       Majed B.
--
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:[~2009-09-17  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  0:13 Raid5 Read stats for parity cal Linux Raid Study
2009-09-17  0:20 ` Majed B. [this message]
2009-09-17  2:38 ` Neil Brown

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=70ed7c3e0909161720r5a068ca4m8335cfbbd51bc220@mail.gmail.com \
    --to=majedb@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=linuxraid.study@gmail.com \
    /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