From: Dexter Filmore <Dexter.Filmore@gmx.de>
To: linux-raid@vger.kernel.org
Subject: scrub was Re: RAID5 Problem - $1000 reward for help
Date: Sun, 17 Sep 2006 14:46:00 +0200 [thread overview]
Message-ID: <200609171446.01130.Dexter.Filmore@gmx.de> (raw)
In-Reply-To: <5b170a7d0609170436w18fc6ff3r713284436c394fa7@mail.gmail.com>
Am Sonntag, 17. September 2006 13:36 schrieben Sie:
> On 9/17/06, Ask Bjørn Hansen <ask@develooper.com> wrote:
> > > It's recommended to use a script to scrub the raid device regularly,
> > > to detect sleeping bad blocks early.
> >
> > What's the best way to do that? dd the full md device to /dev/null?
>
> echo check >/sys/block/md?/md/sync_action
>
> Distros may have cron scripts to do this "right".
>
> And you need a fairly recent kernel.
Does this test stress the discs a lot, like a resync?
How long does it take?
Can I use it on a mounted array?
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a- C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------
http://www.stop1984.com
http://www.againsttcpa.com
-
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
next prev parent reply other threads:[~2006-09-17 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 9:08 RAID5 Problem - $1000 reward for help Reza Naima
2006-09-15 9:47 ` Ask Bjørn Hansen
2006-09-17 7:37 ` Tuomas Leikola
2006-09-17 10:55 ` Ask Bjørn Hansen
2006-09-17 11:36 ` Tuomas Leikola
2006-09-17 12:46 ` Dexter Filmore [this message]
2006-09-17 13:21 ` scrub was " Tuomas Leikola
2006-09-21 18:45 ` Rob Bray
-- strict thread matches above, loose matches on Subject: below --
2006-09-21 20:20 linux
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=200609171446.01130.Dexter.Filmore@gmx.de \
--to=dexter.filmore@gmx.de \
--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).