From: Neil Brown <neilb@suse.de>
To: Daniel Boggs <BecauseImAwesome@Live.com>, linux-raid@vger.kernel.org
Subject: Re: Searching, but not finding...
Date: Tue, 11 May 2010 06:54:17 +1000 [thread overview]
Message-ID: <20100511065417.204d585e@notabene.brown> (raw)
In-Reply-To: <AANLkTinwZPdZw_kUEaV4wHRAI4n0hstu970_lyU04jt_@mail.gmail.com>
On Mon, 10 May 2010 13:07:44 -0700
Daniel Boggs <BecauseImAwesome@Live.com> wrote:
> My apologies Neil,
>
> I tried to follow your direction and e-mail linux-raid@vger.kernel.org with
> the below e-mail, but it was returned as no longer valid. I do not wish to
> bother you, and if you can redirect me to a better place to ask the below
> question, I will happily take direction.
linux-raid@vger.kernel.org definitely works, and I have taken the liberty of
copying this reply to that list.
I believe that vger.kernel.org is configured to reject mail containing HTML,
and you mail did contain HTML, so maybe that was the problem.
>
>
> After years of trial and error I am finally transferring my entire RAID to
> linux as a software RAID. I have wanted to do it for some time, but just
> did not have the linux expertise to get it done. My RAID 6 is building as I
> write this, but this is one feature I have not been able to locate. Most of
> the hardware RAID I have used in the past had something called "Dynamic
> Sector Repair" where it would do a low impact check through the raid to
> confirm and dynamically repair any damaged sectors or data. This is an
> amazing capability since it drastically reduces the likelihood of a
> catastrophic failure during a drive rebuild or some similar action. Does
> mdadm have this capability at all? Would it be possible to add it? If not,
> are you aware of any apps that could?
We call this "scrubbing" mostly, and it is effecfed by:
echo check > /sys/block/mdXX/md/sync_action
This will cause the array to read every block and check for consistency. If
it hits a read error it will handle it the way all read errors are handled,
which is to compute the correct data from else where and write it back so the
drive has a chance to repair or relocate the sector.
It would probably make sense to add a function to mdadm to do this so that it
would be better documented by I haven't yet (though I accept patches....)
NeilBrown
>
> If this is written in the documentation and I just missed it I apologize.
> My understanding of linux is still on the low end. Thank you for your
> time!
>
>
> Daniel
next parent reply other threads:[~2010-05-10 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTik7Ekdhv5qGMzyMu0Q5XhKq7JbaxZFLX6SKl5Zu@mail.gmail.com>
[not found] ` <AANLkTinwZPdZw_kUEaV4wHRAI4n0hstu970_lyU04jt_@mail.gmail.com>
2010-05-10 20:54 ` Neil Brown [this message]
2010-05-10 22:49 ` Searching, but not finding Daniel Boggs
2010-05-10 23:22 ` Neil Brown
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=20100511065417.204d585e@notabene.brown \
--to=neilb@suse.de \
--cc=BecauseImAwesome@Live.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox