All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: still crashing osds with next branch
Date: Thu, 21 Jun 2012 07:54:59 +0200	[thread overview]
Message-ID: <4FE2B733.7010103@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206201554530.14284@cobra.newdream.net>

Am 21.06.2012 00:56, schrieb Sage Weil:
> Just a quick update: there were some problems with doing a rolling
> upgrade that may be responsible for these.  We're testing the fix now.
>
> Did this, by chance, happen on a cluster with a mix of 0.47.2 and 0.48?

No it was a clean install of the next branch. Just two hours old.

Stefan

      reply	other threads:[~2012-06-21  5:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 10:03 still crashing osds with next branch Stefan Priebe - Profihost AG
2012-06-20 13:30 ` Stefan Priebe - Profihost AG
2012-06-20 17:19   ` Stefan Priebe
2012-06-20 17:35     ` Sage Weil
2012-06-20 18:10       ` Stefan Priebe
2012-06-20 18:11         ` Sage Weil
2012-06-20 20:21           ` Stefan Priebe
2012-06-20 22:56     ` Sage Weil
2012-06-21  5:54       ` Stefan Priebe - Profihost AG [this message]

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=4FE2B733.7010103@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.