Ceph is a distributed object, block, and file storage platform
Go to file
Sage Weil 613c8f1edf client: clear I_COMPLETE on traceless reply for dentry request
If a request is against a dentry, and we get a traceless reply, clear
the directory I_COMPLETE flag on the parent directory because we can no
longer trust that our cache is complete.

It is possible we could do something a bit more intelligent here, but it
is not trivial because of racing requests, and traceless replies are
rare, so it's not worth the effort.

Signed-off-by: Sage Weil <sage@inktank.com>
2013-03-07 16:09:45 -08:00
admin
ceph-object-corpus@0655429f62 fix ceph-object-corpus submodule commit 2013-02-27 21:04:49 -08:00
debian Missed adding rados_types.hpp to package 2013-03-06 14:40:29 -08:00
doc release-process.rst: Fix typos 2013-03-05 22:08:15 -08:00
fusetrace
keys
m4
man man: make the cephfs man page marginally more truthful 2013-02-19 17:48:26 -08:00
qa testing: updating hadoop-internal test 2013-02-26 10:53:35 -08:00
src client: clear I_COMPLETE on traceless reply for dentry request 2013-03-07 16:09:45 -08:00
udev udev: trigger on dmcrypted osd partitions 2013-02-15 14:18:34 -08:00
wireshark wireshark/ceph/packet-ceph.c: fix some issues from cppcheck 2013-02-14 10:27:40 -08:00
.gitignore
.gitmodules remove leveldb from master branch 2013-02-27 14:22:48 +01:00
AUTHORS
autogen.sh Build: Change build to always use system leveldb 2013-02-26 20:07:49 -08:00
ceph.spec.in Missed adding rados_types.hpp to package 2013-03-06 14:40:29 -08:00
ChangeLog
CodingStyle
configure.ac Merge branch 'next' 2013-03-05 09:05:21 -08:00
COPYING
COPYING-LGPL2.1
do_autogen.sh
Doxyfile
INSTALL
Makefile.am
NEWS
PendingReleaseNotes PendingReleaseNotes: mention ceph-mon requiring the creation of data dir 2013-02-26 23:47:51 +00:00
README README: Add libsnappy-dev to build requirements. 2013-03-01 23:32:54 -08:00
RELEASE_CHECKLIST
SubmittingPatches

============================================
Ceph - a scalable distributed storage system
============================================

Please see http://ceph.com/ for current info.

Contributing Code
=================

Most of Ceph is licensed under the LGPL version 2.1.  Some
miscellaneous code is under BSD-style license or is public domain.
The documentation is licensed under Creative Commons
Attribution-ShareAlike (CC BY-SA).  There are a handful of headers
included here that are licensed under the GPL.  Please see the file
COPYING for a full inventory of licenses by file.

Code contributions must include a valid "Signed-off-by" acknowledging
the license for the modified or contributed file.  Please see the file
SubmittingPatches for details on what that means and on how to
generate and submit patches.

We do not require assignment of copyright to contribute code; code is
contributed under the terms of the applicable license.


Building Ceph
=============

To prepare the source tree after it has been git cloned,

	$ git submodule update --init

To build the server daemons, and FUSE client, execute the following:

	$ ./autogen.sh
	$ ./configure
	$ make

(Note that the FUSE client will only be built if libfuse is present.)

Dependencies
------------

The configure script will complain about any missing dependencies as
it goes.  You can also refer to debian/control or ceph.spec.in for the
package build dependencies on those platforms.  In many cases,
dependencies can be avoided with --with-foo or --without-bar switches.
For example,

$ ./configure --with-nss         # use libnss instead of libcrypto++
$ ./configure --without-radosgw  # do not build radosgw and avoid libfcgi-dev
$ ./configure --without-tcmalloc # avoid google-perftools dependency


Building packages
-----------------

You can build packages for Debian or Debian-derived (e.g., Ubuntu)
systems with

$ sudo apt-get dpkg-dev
$ dpkg-checkbuilddeps        # make sure we have all dependencies
$ dpkg-buildpackage

For RPM-based systems (Redhat, Suse, etc.),

$ rpmbuild


Building the Documentation
==========================

Prerequisites
-------------
To build the documentation, you must install the following:

- python-dev
- python-pip
- python-virualenv
- doxygen
- ditaa
- libxml2-dev
- libxslt-dev
- dot
- graphviz

For example:

	sudo apt-get install python-dev python-pip python-virualenv doxygen ditaa libxml2-dev libxslt-dev dot graphviz

Building the Documentation
--------------------------

To build the documentation, ensure that you are in the top-level `/ceph directory, and execute the build script. For example:

	$ admin/build-doc


Build Prerequisites
-------------------
To build the source code, you must install the following:

- automake
- autoconf
- automake
- gcc
- g++
- libboost-dev
- libedit-dev
- libssl-dev
- libtool
- libfcgi
- libfcgi-dev
- libfuse-dev
- linux-kernel-headers
- libcrypto++-dev
- libaio-dev
- libgoogle-perftools-dev
- libkeyutils-dev
- uuid-dev
- libatomic-ops-dev
- libboost-program-options-dev
- libboost-thread-dev
- libexpat1-dev
- libleveldb-dev
- libsnappy-dev

For example:

	$ apt-get install automake autoconf automake gcc g++ libboost-dev libedit-dev libssl-dev libtool libfcgi libfcgi-dev libfuse-dev linux-kernel-headers libcrypto++-dev libaio-dev libgoogle-perftools-dev libkeyutils-dev uuid-dev libatomic-ops-dev libboost-program-options-dev libboost-thread-dev libexpat1-dev