Ceph is a distributed object, block, and file storage platform
Go to file
Sage Weil 1908c06149 osd/ECBackend: fix on_write ordering w/ sync onreadable callbacks
When we call handle_sub_write after a write completion, we may
do a sync read completion and then call back into check_ops().  Attaching
the on_write events to the op we're applying means that we don't ensure
that the on_write event(s) happen before the next write in the queue
is submitted (when we call back into check_ops()).

For example, if we have op A, on_write event W, then op B, a sync
applied completion would mean that we would queue the write for A, call
back into SubWriteApplied -> handle_sub_write_reply -> check_ops and then
process B... before getting to W.

Resolve this by attaching the on_write callback to a separate Op that is
placed into the queue, just like any other Op.  This keeps the ordering
logic clean, although it is a bit ugly with the polymorphism around Op
being either an Op or an on_write callback.

Signed-off-by: Sage Weil <sage@redhat.com>
2017-12-12 11:21:49 -06:00
admin
alpine
bin
ceph-erasure-code-corpus@2d7d78b9cc
ceph-object-corpus@420d02a8a2
cmake/modules cmake: disable FAIL_ON_WARNINGS for rocksdb 2017-12-11 14:09:45 +08:00
debian debian/control: adjust ceph-{osdomap,kvstore,monstore}-tool feature move 2017-12-08 14:51:08 +08:00
doc doc: correct the new fs allow opts 2017-12-11 13:32:59 +01:00
etc cmake: only create sysctl file on linux 2017-11-20 15:45:03 +08:00
examples
fusetrace
keys
man
mirroring
qa Merge pull request #18752 from liewegas/wip-peering-queue 2017-12-07 19:43:16 -06:00
selinux
share
src osd/ECBackend: fix on_write ordering w/ sync onreadable callbacks 2017-12-12 11:21:49 -06:00
systemd
udev udev: Fix typo in udev OSD rules file 2017-11-17 11:31:38 -06:00
.gitattributes
.githubmap .githubmap, .mailmap, .organizationmap, .peoplemap: update Igor 2017-12-04 12:14:15 +03:00
.gitignore
.gitmodule_mirrors
.gitmodules
.mailmap .githubmap, .mailmap, .organizationmap, .peoplemap: update Igor 2017-12-04 12:14:15 +03:00
.organizationmap .githubmap, .mailmap, .organizationmap, .peoplemap: update Igor 2017-12-04 12:14:15 +03:00
.peoplemap .githubmap, .mailmap, .organizationmap, .peoplemap: update Igor 2017-12-04 12:14:15 +03:00
AUTHORS
ceph.spec.in ceph.spec: use dts-7 on rhel 2017-12-09 11:18:27 +08:00
CMakeLists.txt Merge pull request #19202 from tchaikov/wip-check-pthread-ext 2017-12-01 10:36:21 +08:00
CodingStyle
CONTRIBUTING.rst
COPYING
COPYING-GPL2
COPYING-LGPL2.1
do_cmake.sh
do_freebsd.sh cmake: WITH_SPDK=ON by default 2017-11-17 15:40:00 +08:00
doc_deps.deb.txt
Doxyfile
install-deps.sh install-deps.sh: install new gcc as the default the right way 2017-12-09 20:00:28 +08:00
make-apk.sh
make-debs.sh
make-dist make-dist: exclude unused bits in boost 2017-11-24 19:16:07 +08:00
make-srpm.sh
PendingReleaseNotes client: quit on failed remount during dentry invalidate test 2017-12-04 16:10:27 -08:00
pom.xml
README.aix
README.alpine.md
README.FreeBSD
README.git-subtree
README.md
README.solaris
README.xio
run-make-check.sh install-deps.sh: use DTS on centos if GCC is too old 2017-12-08 19:36:58 +08:00
SubmittingPatches.rst

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.rst 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.

Checking out the source

You can clone from github with

git clone git@github.com:ceph/ceph

or, if you are not a github user,

git clone git://github.com/ceph/ceph

Ceph contains many git submodules that need to be checked out with

git submodule update --init --recursive

Build Prerequisites

The list of Debian or RPM packages dependencies can be installed with:

./install-deps.sh

Building Ceph

Note that these instructions are meant for developers who are compiling the code for development and testing. To build binaries suitable for installation we recommend you build deb or rpm packages, or refer to the ceph.spec.in or debian/rules to see which configuration options are specified for production builds.

Prerequisite: CMake 2.8.12

Build instructions:

./do_cmake.sh
cd build
make

This assumes you make your build dir a subdirectory of the ceph.git checkout. If you put it elsewhere, just replace .. in do_cmake.sh with a correct path to the checkout.

To build only certain targets use:

make [target name]

To install:

make install

CMake Options

If you run the cmake command by hand, there are many options you can set with "-D". For example the option to build the RADOS Gateway is defaulted to ON. To build without the RADOS Gateway:

cmake -DWITH_RADOSGW=OFF [path to top level ceph directory]

Another example below is building with debugging and alternate locations for a couple of external dependencies:

cmake -DLEVELDB_PREFIX="/opt/hyperleveldb" -DOFED_PREFIX="/opt/ofed" \
-DCMAKE_INSTALL_PREFIX=/opt/accelio -DCMAKE_C_FLAGS="-O0 -g3 -gdwarf-4" \
..

To view an exhaustive list of -D options, you can invoke cmake with:

cmake -LH

If you often pipe make to less and would like to maintain the diagnostic colors for errors and warnings (and if your compiler supports it), you can invoke cmake with:

cmake -DDIAGNOSTICS_COLOR=always ..

Then you'll get the diagnostic colors when you execute:

make | less -R

Other available values for 'DIAGNOSTICS_COLOR' are 'auto' (default) and 'never'.

Building a source tarball

To build a complete source tarball with everything needed to build from source and/or build a (deb or rpm) package, run

./make-dist

This will create a tarball like ceph-$version.tar.bz2 from git. (Ensure that any changes you want to include in your working directory are committed to git.)

Running a test cluster

To run a functional test cluster,

cd build
make vstart        # builds just enough to run vstart
../src/vstart.sh --debug --new -x --localhost --bluestore
./bin/ceph -s

Almost all of the usual commands are available in the bin/ directory. For example,

./bin/rados -p rbd bench 30 write
./bin/rbd create foo --size 1000

To shut down the test cluster,

../src/stop.sh

To start or stop individual daemons, the sysvinit script can be used:

./bin/init-ceph restart osd.0
./bin/init-ceph stop

Running unit tests

To build and run all tests (in parallel using all processors), use ctest:

cd build
make
ctest -j$(nproc)

(Note: Many targets built from src/test are not run using ctest. Targets starting with "unittest" are run in make check and thus can be run with ctest. Targets starting with "ceph_test" can not, and should be run by hand.)

When failures occur, look in build/Testing/Temporary for logs.

To build and run all tests and their dependencies without other unnecessary targets in Ceph:

cd build
make check -j$(nproc)

To run an individual test manually, run ctest with -R (regex matching):

ctest -R [regex matching test name(s)]

(Note: ctest does not build the test it's running or the dependencies needed to run it)

To run an individual test manually and see all the tests output, run ctest with the -V (verbose) flag:

ctest -V -R [regex matching test name(s)]

To run an tests manually and run the jobs in parallel, run ctest with the -j flag:

ctest -j [number of jobs]

There are many other flags you can give ctest for better control over manual test execution. To view these options run:

man ctest

Building the Documentation

Prerequisites

The list of package dependencies for building the documentation can be found in doc_deps.deb.txt:

sudo apt-get install `cat doc_deps.deb.txt`

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