From: Mike Hardy <mhardy@h3c.com>
To: Mark Hahn <hahn@physics.mcmaster.ca>, linux-raid@vger.kernel.org
Subject: Re: Raid 1 install revealed poor HD performance (I think)
Date: Wed, 18 May 2005 08:08:46 -0700 [thread overview]
Message-ID: <428B5A7E.2050509@h3c.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0505180206580.1777-100000@coffee.psychology.mcmaster.ca>
All colo facilities are required to have a complete power cut-off switch
for fire fighter safety. Its behind the UPS stacks, specifically so that
they know the racks aren't energized before they go in.
Apparently, the big red button that activates this cutoff is an easy
target for people to accidentally lean on or similar, so all power goes
down immediately.
http://www.google.com/search?q=data+corruption+colocation+power+cut+off+write+caching
As an example, the first result there is for wikipedia, which you've
probably heard of ;-)
LiveJournal (another huge site) was also bit by this.
Bottom line is, if you are in a colo, there must be a switch between all
power service and your machines, so you are susceptible
Posted back to linux-raid for general interest. Maybe everyone else
isn't interested, but I'm fascinated by gotchas. I'm sure at least a few
others...
-Mike
Mark Hahn wrote:
>>In particular, drives like to enable write-caching out of the box now,
>>which opens a window for data corruption that has bitten more than a few
>>high-profile sites as it causes the disk to break the fsync contract
>
>
> I'm curious for details on which sites and how they broke.
> I can't think of a scenario (except perhaps operating a server
> without UPS) were this would be a problem. maybe servers
> that are otherwise in such bad shape that they crash?
next parent reply other threads:[~2005-05-18 15:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0505180206580.1777-100000@coffee.psychology.mcmaster.ca>
2005-05-18 15:08 ` Mike Hardy [this message]
2005-05-17 15:11 Raid 1 install revealed poor HD performance (I think) Jay Strauss
2005-05-17 15:50 ` Gordon Henderson
2005-05-17 16:17 ` Jay Strauss
2005-05-17 16:23 ` Gordon Henderson
2005-05-17 16:52 ` Mike Hardy
2005-05-17 20:51 ` Jay Strauss
2005-05-17 20:54 ` Mike Hardy
2005-05-17 22:16 ` Tobias Hofmann
2005-05-17 23:00 ` Jay Strauss
2005-05-18 3:28 ` Jay Strauss
2005-05-17 22:45 ` Peter T. Breuer
2005-05-17 23:42 ` Henrik Holst
2005-05-18 3:30 ` Jay Strauss
2005-05-17 23:44 ` Henrik Holst
2005-05-19 15:32 ` Jay Strauss
2005-05-19 16:14 ` Mike Hardy
2005-05-19 18:40 ` Jay Strauss
2005-05-19 20:43 ` Mike Hardy
2005-05-20 1:43 ` Jay Strauss
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=428B5A7E.2050509@h3c.com \
--to=mhardy@h3c.com \
--cc=hahn@physics.mcmaster.ca \
--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).