From: geoff@plan9.bell-labs.com
To: 9fans@9fans.net
Subject: Re: [9fans] Bell Labs Plan 9 pages are down
Date: Fri, 1 Oct 2010 00:29:26 -0400 [thread overview]
Message-ID: <3f35877279b09e591178c4308b44bdf1@plan9.bell-labs.com> (raw)
In-Reply-To: <09B3896D-CBFF-4374-AADD-15CB35669821@gmail.com>
Our main file server, after 215 days of up time, started getting
processes stuck in Fauth state and it spread to our cpu servers.
Restarting our authentication server and the main cpu servers
didn't fix it, so I took down the whole complex, turned the machines
off for a few minutes and restarted them all.
Things should be back to normal now.
next prev parent reply other threads:[~2010-10-01 4:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 13:36 [9fans] IBM Research Internship Position Available Eric Van Hensbergen
2010-09-23 13:45 ` Mathieu Lonjaret
2010-09-23 14:28 ` Eric Van Hensbergen
2010-09-30 19:56 ` Eric Van Hensbergen
2010-10-01 2:33 ` Anssi Porttikivi
2010-10-01 2:37 ` [9fans] Bell Labs Plan 9 pages are down Anssi Porttikivi
2010-10-01 4:29 ` geoff [this message]
2010-10-01 13:30 ` [9fans] IBM Research Internship Position Available Eric Van Hensbergen
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=3f35877279b09e591178c4308b44bdf1@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--cc=9fans@9fans.net \
/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).