From: Vitaly Shishakov <shift@cmpd2.phys.msu.su>
To: ceph-devel@lists.sourceforge.net
Subject: build ceph 0.17 on OpenSuSE 11.0 (success)
Date: Wed, 25 Nov 2009 07:35:28 +0300 [thread overview]
Message-ID: <4B0CB410.7070701@cmpd2.phys.msu.su> (raw)
I tried to build ceph-0.17 on OpenSUSE 11.0 (default kernel - 2.6.25,
libfuse 2.8 upgraded from repository, default version is 2.7)
to do that i had to make the following changes:
1) install more fresh version on BOOST (default version was 1.34, i
installed 1.39 from repositories),
and other prereqs, like libedit-devel, fuse-devel, etc.
2) change src/include/object.h -- add #include <stdio.h> -- to
suppress error about not found sprintf function
3) change dependencies in ceph.spec --
(i actually removed them, only left build_reqs and relied on automagical
dependency discovery)
4) in .spec file I commented out everything about kernel client, due to
some kernel requirements
(like unaligned access functions. at first i )
i only left FUSE client, and added those files, that were missing.
then i built rpms, which i used to distribute along my cluster nodes.
20 nodes, 1 managing server, 1Gbit network.
each node has 6x640GB SATA HDD !
so far i tested with 4 nodes, each hosting 1 OSD based on ext3 volume. +
1mon and 1msd.
i have to say, that bonnie++ went successfully, showing 50MB/sec,
same as NFS on the same network (seems like bad ethernet card or bad switch)
more tests to come.
the only problem so far: cfuse-mounted filesystem refuse to unmount.
(says that device is busy)
I have to admit: far more easier deployment, than with Lustre!
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
reply other threads:[~2009-11-25 4:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B0CB410.7070701@cmpd2.phys.msu.su \
--to=shift@cmpd2.phys.msu.su \
--cc=ceph-devel@lists.sourceforge.net \
/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.