From: Al Boldi <a1426z@gawab.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH md ] Better handling of readerrors with raid5.
Date: Wed, 21 Sep 2005 18:07:24 +0300 [thread overview]
Message-ID: <200509211807.24194.a1426z@gawab.com> (raw)
In-Reply-To: <17201.9323.915024.189868@cse.unsw.edu.au>
Neil Brown wrote:
> I'm nearly ready to give away a patch which does a background parity
> check - it reads all blocks and checks parity, and reports the error
> count etc. Running such a thing every night (or every week) is
> probably a good idea in some situations, but really needs the
> fix-read-errors patch.
I love it!
Thanks!
--
Al
next prev parent reply other threads:[~2005-09-21 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050916125754.11044.patches@notabene>
2005-09-16 3:01 ` [PATCH md ] Better handling of readerrors with raid5 NeilBrown
2005-09-16 16:53 ` Mike Hardy
2005-09-16 21:39 ` Neil Brown
2005-09-18 22:06 ` JaniD++
2005-09-21 0:15 ` Molle Bestefich
2005-09-21 9:14 ` Neil Brown
2005-09-21 15:07 ` Al Boldi [this message]
2005-10-23 3:57 ` Patrik Jonsson
2005-10-23 22:52 ` Neil Brown
2005-10-11 14:31 ` Mattias Wadenstein
2005-12-22 22:23 ` Stephan van Hienen
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=200509211807.24194.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).