All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
To: Wols Lists <antlists@youngman.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Disk Monitoring
Date: Fri, 30 Jun 2017 14:35:18 +0200	[thread overview]
Message-ID: <CAJH6TXg+xf0giY5bC_ug4jm+t88LzHkTVJq_BYeYzxEKedF2OA@mail.gmail.com> (raw)
In-Reply-To: <59550FCB.4090508@youngman.org.uk>

2017-06-29 16:33 GMT+02:00 Wols Lists <antlists@youngman.org.uk>:
> 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.)

Ok, so, if resources are not a problem, someone could only run a
consistency check and totally skip the patrol check. Right ?

What about md reliability? There are many detractors out there.

https://bugzilla.kernel.org/show_bug.cgi?id=99171

One of the most common complaint is the absence of write-back cache,
and if you force a "writeback" you'll risk data loss in case of
unclean shutdown (power failure and so on)

  reply	other threads:[~2017-06-30 12:35 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
2017-06-30 12:35         ` Gandalf Corvotempesta [this message]
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=CAJH6TXg+xf0giY5bC_ug4jm+t88LzHkTVJq_BYeYzxEKedF2OA@mail.gmail.com \
    --to=gandalf.corvotempesta@gmail.com \
    --cc=antlists@youngman.org.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 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.