All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Tripathy <jonnyt@abpni.co.uk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: Resync Every Sunday
Date: Sun, 01 Jul 2012 13:53:22 +0100	[thread overview]
Message-ID: <4FF04842.9080806@abpni.co.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1207011412270.27169@uplift.swm.pp.se>


On 01/07/2012 13:44, Mikael Abrahamsson wrote:
> On Sun, 1 Jul 2012, Jonathan Tripathy wrote:
>
>> - Is it safe to disable these checks? Would monitoring the SMART 
>> status of the disks serve as a good substitute?
>
> Well, that's a decision you will have to make for yourself. The 
> rationale behind it is to find latent read errors and correct them 
> while you have parity already. Another term for this is "data 
> scrubbing", you'll find quite a lot of discussion on that topic.
>
> Personally, my view is that I make sure all my data are read at least 
> once a month, I have experienced data loss historically because of 
> lack of scrubbing.
>
Thanks, I think I'll change it to monthly as well. That seems like a 
good compromise.

I'm still very interested in the other questions though. Especially the 
one relating to why not all arrays are checked

Thanks

  reply	other threads:[~2012-07-01 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-01 11:20 Resync Every Sunday Jonathan Tripathy
2012-07-01 12:04 ` Jonathan Tripathy
2012-07-01 12:44   ` Mikael Abrahamsson
2012-07-01 12:53     ` Jonathan Tripathy [this message]
2012-07-01 20:41 ` Keith Keller
2012-07-01 20:44   ` Jonathan Tripathy
2012-07-01 21:24     ` Larkin Lowrey
2012-07-01 21:57       ` Jonathan Tripathy
2012-07-01 22:01         ` Jonathan Tripathy
2012-07-02 17:06           ` Larkin Lowrey
2012-07-02 21:30             ` Keith Keller
2012-07-02 22:55               ` Jonathan Tripathy
2012-07-03  3:33                 ` Keith Keller

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=4FF04842.9080806@abpni.co.uk \
    --to=jonnyt@abpni.co.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=swmike@swm.pp.se \
    /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.