From: Dan Mick <dan.mick@inktank.com>
To: hemant surale <work.hemant.surale@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Unable to build Ceph from source code
Date: Thu, 18 Oct 2012 19:24:11 -0700 [thread overview]
Message-ID: <5080B9CB.2030209@inktank.com> (raw)
In-Reply-To: <CAAY-_OEHukt7ESqyxHQx4Bp_Vx6ui8ahy1UwESC25E7SZ0vE3A@mail.gmail.com>
On 10/17/2012 09:58 PM, hemant surale wrote:
> Hi Community,
> I have tried to build ceph from source code i.e. v0.48 tarball .
> After proceeding to all steps given at official site . when I execute
> "service ceph start " it gives following error
>
> -----------------//Error ------------------------------------
> root@atish-virtual-machine:~# service ceph start
> /etc/init.d/ceph: 37: .: Can't open /usr/lib/ceph/ceph_common.sh
> -----------------------------------------------------------------
So, clearly something went wrong with the installation step, and this
file was not created. How did you install after building?
> As well as I have created ceph.conf .. and when I execute "mkcephfs -a
> -c /usr/local/bin/ceph.conf -k ceph.keyring" it gives following error
>
> -----------------//Error ------------------------------------
> temp dir is /tmp/mkcephfs.fwMGAd6Qko
> preparing monmap in /tmp/mkcephfs.fwMGAd6Qko/monmap
> /usr/local/bin/monmaptool --create --clobber --add alpha
> 10.72.148.248:6789 --print /tmp/mkcephfs.fwMGAd6Qko/monmap
> /usr/local/bin/monmaptool: monmap file /tmp/mkcephfs.fwMGAd6Qko/monmap
> /usr/local/bin/monmaptool: generated fsid 390b4802-a482-4d28-98ea-e5437881b22b
> epoch 0
> fsid 390b4802-a482-4d28-98ea-e5437881b22b
> last_changed 2012-10-17 16:57:30.446192
> created 2012-10-17 16:57:30.446192
> 0: 10.72.148.248:6789/0 mon.alpha
> /usr/local/bin/monmaptool: writing epoch 0 to
> /tmp/mkcephfs.fwMGAd6Qko/monmap (1 monitors)
> === osd.0 ===
> 2012-10-17 16:57:30.550339 b6fb3740 -1
> filestore(/var/lib/ceph/osd/ceph-0) limited size xattrs -- enable
> filestore_xattr_use_omap
^^ this is a pretty good clue. It says the filesystem you've chosen for
your OSD has limited size for storing xattrs. You should enable the
filestore_xattr_use_omap option. See
http://ceph.com/docs/master/config-cluster/file-system-recommendations/
> 2012-10-17 16:57:30.550399 b6fb3740 -1 OSD::mkfs: couldn't mount
> FileStore: error -95
> 2012-10-17 16:57:30.550440 b6fb3740 -1 ** ERROR: error creating empty
> object store in /var/lib/ceph/osd/ceph-0: (95) Operation not supported
> failed: '/usr/local/sbin/mkcephfs -d /tmp/mkcephfs.fwMGAd6Qko
> --init-daemon osd.0'
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Please help me out. Thanks in advance
>
> -
> Hemant Surale.
> --
> 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
>
prev parent reply other threads:[~2012-10-19 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 4:58 Unable to build Ceph from source code hemant surale
2012-10-19 2:24 ` Dan Mick [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=5080B9CB.2030209@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=work.hemant.surale@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox