From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Xiaopong Tran <xiaopong.tran@gmail.com>
Cc: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: Strange behavior after upgrading to 0.48
Date: Fri, 06 Jul 2012 16:14:28 +1200 [thread overview]
Message-ID: <4FF66624.1040607@catalyst.net.nz> (raw)
In-Reply-To: <4FF64FB7.90709@gmail.com>
On 06/07/12 14:38, Xiaopong Tran wrote:
>
> Thanks for the quick reply, I didn't have the computer with me last
> night. But you were right. I checked the version of ceph on ubuntu,
> and it's still stuck with 0.47.3, despite upgrading. I redid the
> upgrade, and it's still stuck with that version. That's something
> I didn't pay attention to.
>
> I had to purge the ceph, ceph-common and other related packages,
> and re-install it, then I got 0.48. And now ceph -s works just
> as it should.
>
> So, somehow, the upgrade on ubuntu does not work properly.
>
> Thinking about this issue just right now, I think ceph -s
> still worked right because there was still an older version
> of mon when the first two nodes were being upgraded. When
> the last one was upgraded, there's no mon of the same version
> anymore.
>
> Sorry, should have checked if apt upgrade was done properly
> first :)
>
>
FYI: I ran into this too - you need to do:
apt-get dist-upgrade
for the 0.47-2 packages to be replaced by 0.48 (of course purging 'em
and reinstalling works too...just a bit more drastic)!
regards
Mark
next prev parent reply other threads:[~2012-07-06 4:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 6:41 Strange behavior after upgrading to 0.48 Xiaopong Tran
2012-07-05 6:47 ` Xiaopong Tran
2012-07-05 14:26 ` Sage Weil
2012-07-05 14:35 ` Xiaopong Tran
2012-07-05 14:38 ` Sage Weil
2012-07-06 2:38 ` Xiaopong Tran
2012-07-06 4:14 ` Mark Kirkwood [this message]
2012-07-06 4:17 ` Sage Weil
2012-07-06 4:52 ` Mark Kirkwood
2012-07-06 5:07 ` Sage Weil
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=4FF66624.1040607@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=xiaopong.tran@gmail.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.