All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Disk Monitoring
Date: Thu, 29 Jun 2017 15:33:47 +0100	[thread overview]
Message-ID: <59550FCB.4090508@youngman.org.uk> (raw)
In-Reply-To: <CAJH6TXiONYigcX1CtQw86ZXUgeOLvzD_+2couNfxSwL9hHj1gA@mail.gmail.com>

On 29/06/17 11:16, Gandalf Corvotempesta wrote:
> 2017-06-29 12:14 GMT+02:00 Mateusz Korniak <mateusz-lists@ant.gliwice.pl>:
>> One can read of all disks/partitions used by RAIDs by script
>> /usr/share/mdadm/checkarray
>>
>> In many distros it is set to be performed monthly out-of-box.
> 
> I know this and I'm running weekly. (just to be sure)
> What Is unclear to me is why an hardware raid controller like LSI, has
> two different kind of checks: patrol read and consistency check.

Because they're two completely different things.

A patrol check reads the entire disk. It doesn't give two hoots what the
data is, it just cares that the data can actually be retrieved from the
disk.

A consistency check, on the other hand, wants to make sure that the data
is correct. It will read both copies of a mirror and compare them. Or it
will read the data from 4/5/6, calculate the parities, then read them
from disk and compare them.

In other words, a patrol check looks for a failing disk. A consistency
check looks for corrupt data. (A consistency check does a patrol check
as a side effect, but you might not want to do just that, as it is
computationally much more expensive. You might want to do a patrol check
every day, and a consistency check of a weekend.)

Cheers,
Wol


  reply	other threads:[~2017-06-29 14:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 13:19 Disk Monitoring Wolfgang Denk
2017-06-29  9:52 ` Gandalf Corvotempesta
2017-06-29 10:10   ` Reindl Harald
2017-06-29 10:14     ` Gandalf Corvotempesta
2017-06-29 10:37       ` Reindl Harald
2017-06-29 14:28       ` Wols Lists
2017-06-29 10:14   ` Andreas Klauer
2017-06-29 10:14   ` Mateusz Korniak
2017-06-29 10:16     ` Gandalf Corvotempesta
2017-06-29 14:33       ` Wols Lists [this message]
2017-06-30 12:35         ` Gandalf Corvotempesta
2017-06-30 14:35           ` Phil Turmel
2017-06-30 19:56             ` Anthony Youngman
2017-07-01 13:42               ` Drew
2017-07-01 14:12                 ` Gandalf Corvotempesta
2017-07-01 15:36                   ` Drew
2017-06-29 10:20   ` Mateusz Korniak
2017-06-29 10:25     ` Gandalf Corvotempesta
2017-06-29 10:34       ` Reindl Harald
  -- strict thread matches above, loose matches on Subject: below --
2017-06-28 10:25 Gandalf Corvotempesta
2017-06-28 10:45 ` Johannes Truschnigg
2017-07-06  3:31   ` NeilBrown
2017-06-28 12:43 ` Wols Lists

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=59550FCB.4090508@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gandalf.corvotempesta@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 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.