From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Peter Chacko <peterchacko35@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
pnfs@linux-nfs.org
Subject: Re: citi, linux-nfs.org downtime
Date: Mon, 22 Jun 2009 13:55:25 -0400 [thread overview]
Message-ID: <1245693325.5182.255.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1f808b4a0906221007x22e6b3f0qab7a750ee2ea2c5f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, 2009-06-22 at 22:37 +0530, Peter Chacko wrote:
> Very bad of you.... should have adopted virtualization and its
> non-disruptive migration benefits :-) :-)
It is non-disruptive only if you have a machine that can host the VM
while the contents of the machine room are being moved. It also assumes
a rich sugar-daddy who can pony up the cash for new processors with vm
extensions... ;-)
Trond
> On Mon, Jun 22, 2009 at 9:56 PM, J. Bruce Fields<bfields@fieldses.org> 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.
> >
> > Also we'll be very busy (and possibly not have access to email), so may
> > not be very responsive for a few days.
> >
> > --b.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-22 17:55 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 [this message]
2009-06-24 21:35 ` J. Bruce Fields
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=1245693325.5182.255.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=peterchacko35@gmail.com \
--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