From: Rik Herrin <rikherrin@yahoo.com>
To: linux-raid@vger.kernel.org
Subject: Re: blog entry on RAID limitation
Date: Sun, 22 Jan 2006 03:52:31 -0800 (PST) [thread overview]
Message-ID: <20060122115231.9294.qmail@web52910.mail.yahoo.com> (raw)
Wouldn't connecting a UPS + using a stable kernel
version remove 90% or so of the "RAID-5 write hole"
problem? Are there any other means to know when this
has occurred?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2006-01-22 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 11:52 Rik Herrin [this message]
2006-01-22 23:08 ` blog entry on RAID limitation Neil Brown
2006-01-27 13:09 ` Molle Bestefich
[not found] <8E5ACAE05E6B9E44A2903C693A5D4E8A097F6C86@hqemmail02.nvidia.com>
2006-01-17 8:45 ` Jeff Breidenbach
2006-01-17 10:40 ` Neil Brown
2006-01-17 16:42 ` Jacob Madsen
2006-01-17 22:47 ` Neil Brown
2006-01-21 20:50 ` Carlos Carvalho
2006-01-24 3:20 ` Neil Brown
2006-01-21 20:43 ` Carlos Carvalho
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=20060122115231.9294.qmail@web52910.mail.yahoo.com \
--to=rikherrin@yahoo.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;
as well as URLs for NNTP newsgroup(s).