public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org, pnfs@linux-nfs.org
Subject: Re: citi, linux-nfs.org downtime
Date: Wed, 24 Jun 2009 17:35:27 -0400	[thread overview]
Message-ID: <20090624213527.GC14503@fieldses.org> (raw)
In-Reply-To: <20090622162611.GB16719@fieldses.org>

On Mon, Jun 22, 2009 at 12:26:11PM -0400, J. Bruce Fields wrote:
> CITI's offices and machine room are moving to a new building tomorrow
> (tuesday).  This means that citi.umich.edu and linux-nfs.org will be
> going down late tonight or early tomorrow morning, and staying down at
> least until early afternoon (and probably longer).
> 
> (Alert users may already have noticed one or two outages of several
> hours over the last few weeks as we prepared the machine room for the
> move.)
> 
> Apologies in advance for any inconvenience--getting services back up
> will be our first priority, but it's a complicated operation.

Stuff should be mostly working again now.

So, if I have this right:

	Total data moved: ~ 35 terabytes
	Time to get racks back online: ~ 28 hours
	Estimated total bandwidth of the CITI move: 2.8 gigabits/second

If we count only the time to physically move the racks, and not the time
to get them back online, bandwidth is closer to 20 gigabits per second.

--b.

  parent reply	other threads:[~2009-06-24 21:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 16:26 citi, linux-nfs.org downtime J. Bruce Fields
2009-06-22 17:07 ` Peter Chacko
     [not found]   ` <1f808b4a0906221007x22e6b3f0qab7a750ee2ea2c5f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-22 17:55     ` Trond Myklebust
2009-06-24 21:35 ` J. Bruce Fields [this message]
2009-06-25  2:38   ` Brian J. Murrell

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=20090624213527.GC14503@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=pnfs@linux-nfs.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