From: Valdis.Kletnieks@vt.edu
To: Ian Kent <raven@themaw.net>
Cc: John Stoffel <john@stoffel.org>,
Peter Staubach <staubach@redhat.com>,
Robin Lee Powell <rlpowell@digitalkingdom.org>,
linux-kernel@vger.kernel.org
Subject: Re: NFS hang + umount -f: better behaviour requested.
Date: Fri, 31 Aug 2007 11:10:02 -0400 [thread overview]
Message-ID: <27240.1188573002@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 31 Aug 2007 16:06:36 +0800." <Pine.LNX.4.64.0708311600120.12745@raven.themaw.net>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Fri, 31 Aug 2007 16:06:36 +0800, Ian Kent said:
> So, there's a power outage and the UPS had a glitch.
Murphy can get a *lot* more creative than that.
So we'd outgrown the capacity on our UPS and diesel generator, and decided
to replace them. So we schedule downtime for a Saturday. Rather scary, we
had a Sun E10K that had been powered-up for several years, and just as expected,
a good fraction of the 400+ drives it had failed to re-spinup. While recovering
from that, we discovered that although the vast majority of the 400 drives were
either mirrors or raidsets, due to a config error, the boot volume wasn't
mirrored (fortunately, it spun up OK so we dodged the bullet), so we fixed that.
Literally the next Friday, not even a week later, a contractor relocating a
door into our machine room shorted out a sensor circuit in our fire suppression
system, triggering a Halon dump. Of course, no amount of UPS and diesel was
going to save us now, because there was a safety interlock that killed the
power feeds if the Halon dumped. This time, since they'd all been stressed
just a week before, only 2 of the 400+ disks on the E10K failed to spin up.
Guess which two. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-08-31 15:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 22:54 Robin Lee Powell
2007-08-20 23:27 ` Neil Brown
2007-08-20 23:34 ` Robin Lee Powell
2007-08-21 1:51 ` Salah Coronya
2007-08-21 16:43 ` John Stoffel
2007-08-21 16:55 ` J. Bruce Fields
2007-08-21 17:01 ` Peter Staubach
2007-08-21 17:14 ` Chakri n
2007-08-21 17:14 ` Robin Lee Powell
2007-08-21 17:18 ` Peter Staubach
2007-08-21 18:50 ` John Stoffel
2007-08-21 19:04 ` Peter Staubach
2007-08-21 19:25 ` J. Bruce Fields
2007-08-24 15:09 ` Ric Wheeler
2007-08-24 15:37 ` Peter Staubach
2007-08-24 15:53 ` J. Bruce Fields
2007-08-21 23:04 ` Valdis.Kletnieks
2007-08-22 10:03 ` Theodore Tso
2007-08-22 15:26 ` John Stoffel
2007-08-31 8:06 ` Ian Kent
2007-08-31 15:10 ` Valdis.Kletnieks [this message]
2007-08-31 15:30 ` Ian Kent
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=27240.1188573002@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=rlpowell@digitalkingdom.org \
--cc=staubach@redhat.com \
/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
all inboxes | Powered by JetHome®