From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xing Lin Subject: Re: which Linux kernel version corresponds to 0.48argonaut? Date: Sun, 06 Jan 2013 00:06:02 -0700 Message-ID: <50E9225A.2050801@cs.utah.edu> References: <50D35ECA.4040602@cs.utah.edu> <50D3BD69.8010305@cs.utah.edu> <50E8D99F.3090008@cs.utah.edu> <50E8E8D1.6010000@catalyst.net.nz> <50E8EAAB.9030501@cs.utah.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rio.cs.utah.edu ([155.98.64.241]:35740 "EHLO mail-svr1.cs.utah.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751043Ab3AFHGG (ORCPT ); Sun, 6 Jan 2013 02:06:06 -0500 In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Sage Weil Cc: Mark Kirkwood , Gregory Farnum , "ceph-devel@vger.kernel.org" It works now. The old version of .so files in /usr/lib are linked, instead of new version of these files which are installed at /usr/local/lib. Thanks, Sage. Xing On 01/05/2013 09:46 PM, Sage Weil wrote: > Hi, > > The rbd binary is dynamically linking to librbd1.so and librados2.so > (usually in /usr/lib). You need to make sure that the .so's you compiled > are the ones it links to to get your code to run. > > sage > > > On Sat, 5 Jan 2013, Xing Lin wrote: > >> 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. >>>> >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >>