From: ptb@lab.it.uc3m.es (Peter T. Breuer)
To: linux-raid@vger.kernel.org
Subject: Re: RAID1 robust read and read/write correct and EVMS-BBR
Date: Wed, 23 Feb 2005 22:30:17 +0100 [thread overview]
Message-ID: <989ve2-9an.ln1@news.it.uc3m.es> (raw)
In-Reply-To: 200502232122.WAA20465@node130.rhm.de
bernd@rhm.de wrote:
> We are waiting for the one day where the same block on all mirrors has
> read problems. Ok, we're now waiting for about 15 years because the
> HPUX mirror strategy is the same. Quite a long time without desaster
> but it will happen (till today Murphy was right in any case but one:-)).
> If anything happens to a disk one must be warned as soon as possible.
Sarky :).
(or did I mean "scary"? |-)
Peter
prev parent reply other threads:[~2005-02-23 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 19:55 RAID1 robust read and read/write correct and EVMS-BBR Nagpure, Dinesh
2005-02-23 20:07 ` J. David Beutel
2005-02-23 20:52 ` Guy
2005-02-23 21:01 ` Peter T. Breuer
2005-02-23 21:22 ` bernd
2005-02-23 21:30 ` Peter T. Breuer [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=989ve2-9an.ln1@news.it.uc3m.es \
--to=ptb@lab.it.uc3m.es \
--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).