linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-raid@vger.kernel.org
Subject: checking md device parity (forced resync) - is it necessary?
Date: Tue, 05 Sep 2006 10:59:17 +0200	[thread overview]
Message-ID: <44FD3C65.8040000@wpkg.org> (raw)

Lately I installed Debian on a Thecus n4100 machine.
It's a 600 MHz ARM storage device, and has 4 x 400 GB drives.

I made Linux software RAID on these drives:
- RAID-1  - ~1 GB for system (/)
- RAID-1  - ~1 GB for swap
- RAID-10 - ~798 GB for iSCSI storage


I noticed that each day the device slows down; a quick investigation 
discovered that Debian runs a "checkarray" script each night at 1 am 
(via cron). The essence of "checkarray" script is basically this:

echo check > /sys/block/$dev/md/sync_action

Which starts a resync of drives. As one can imagine, resync of 800 GB on 
a rather slow device (600 MHz ARM) can take 12 hours or so...


So my question is: is this "daily forced resync" necessary?

Perhaps in some cases, yes, because someone wrote that tool which does 
it daily.

On the other hand, if we consider Linux software RAID stable, such a 
resync would be only needed in some rare situations.

When can one need to run a "daily forced resync", and in which 
circumstances?


-- 
Tomasz Chmielewski

             reply	other threads:[~2006-09-05  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05  8:59 Tomasz Chmielewski [this message]
2006-09-05 10:13 ` checking md device parity (forced resync) - is it necessary? Neil Brown
2006-09-05 12:00   ` Tomasz Chmielewski
2006-09-05 16:59     ` Luca Berra
2006-09-06  7:19     ` Mario 'BitKoenig' Holbe
2006-09-06  8:12       ` Tomasz Chmielewski
2006-09-06 13:55 ` John Stoffel
2006-09-06 14:11   ` Tomasz Chmielewski

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=44FD3C65.8040000@wpkg.org \
    --to=mangoo@wpkg.org \
    --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).