From: John Rowe <rowe@excc.ex.ac.uk>
To: Jim Klimov <klimov@2ka.mipt.ru>
Cc: linux-raid@vger.kernel.org
Subject: Re: Re[2]: Concept problem with RAID1?
Date: Fri, 24 Mar 2006 16:39:46 +0000 [thread overview]
Message-ID: <1143218386.28440.84.camel@kenny> (raw)
In-Reply-To: <392345161.20060324191520@2ka.mipt.ru>
A much nicer way to get that sort of reliability would be for RAID6 to
periodically scan the blocks on the device and to use the extra
information to do ECC (and for RAID5 to at tell syslog).
John
prev parent reply other threads:[~2006-03-24 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 16:15 Re[2]: Concept problem with RAID1? Jim Klimov
2006-03-24 16:39 ` John Rowe [this message]
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=1143218386.28440.84.camel@kenny \
--to=rowe@excc.ex.ac.uk \
--cc=klimov@2ka.mipt.ru \
--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