From: Xing Lin <xinglin@cs.utah.edu>
To: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Sage Weil <sage@inktank.com>, Gregory Farnum <greg@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: which Linux kernel version corresponds to 0.48argonaut?
Date: Sat, 05 Jan 2013 20:08:27 -0700 [thread overview]
Message-ID: <50E8EAAB.9030501@cs.utah.edu> (raw)
In-Reply-To: <50E8E8D1.6010000@catalyst.net.nz>
Hi Mark,
Thanks for your reply. I do not think I am running the packaged version.
The output shows it is my version (0.48.2argonaut.fast at commit 000...).
root@client:/users/utos# rbd -v
ceph version 0.48.2argonaut.fast
(commit:000000000000000000000000000000000000000000000)
root@client:/users/utos# /usr/bin/rbd -v
ceph version 0.48.2argonaut
(commit:3e02b2fad88c2a95d9c0c86878f10d1beb780bfe)
root@client:/users/utos# /usr/local/bin/rbd -v
ceph version 0.48.2argonaut.fast
(commit:000000000000000000000000000000000000000000000)
Xing
On 01/05/2013 08:00 PM, Mark Kirkwood wrote:
> I'd hazard a guess that you are still (accidentally) running the
> packaged binary - the packaged version installs in /usr/bin (etc) but
> your source build will probably be in /usr/local/bin. I've been
> through this myself and purged the packaged version before building
> and installing from source (just to be sure).
>
> Cheers
>
> Mark
>
> On 06/01/13 14:55, Xing Lin wrote:
>
>> After changing the client-side code, I can map/unmap rbd block devices
>> at client machines. However, I am not able to list rbd block devices. At
>> the client machine, I first installed 0.48.2argonaut package for Ubuntu
>> then I compiled and installed my own version according to instructions
>> on this page ( http://ceph.com/docs/master/install/building-ceph/). The
>> client failed to recognize the fifth bucket algorithm I added. I
>> searched "unsupported bucket algorithm" in the ceph code base and that
>> text only appeared in the src/crush/CrushWrapper.cc. I checked
>> decode_crush_bucket() and it should be able to recognize the fifth
>> algorithm. Even after I changed the error message (added print of
>> "[XXX]" and values for two bucket algorithm macros), it still prints the
>> same error message. So, it seems that my new version of CrushWrapper.cc
>> is not used during compilation to create the final rbd binary. Would you
>> please tell me where the problem is and how I can fix it? Thank you very
>> much.
>>
next prev parent reply other threads:[~2013-01-06 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 18:54 which Linux kernel version corresponds to 0.48argonaut? Xing Lin
2012-12-21 1:37 ` Xing Lin
2013-01-05 0:29 ` Gregory Farnum
2013-01-05 0:34 ` Sage Weil
2013-01-06 1:55 ` Xing Lin
2013-01-06 3:00 ` Mark Kirkwood
2013-01-06 3:08 ` Xing Lin [this message]
2013-01-06 4:46 ` Sage Weil
2013-01-06 7:06 ` Xing Lin
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=50E8EAAB.9030501@cs.utah.edu \
--to=xinglin@cs.utah.edu \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=mark.kirkwood@catalyst.net.nz \
--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.