glusterfs

History

Amar Tumballi 0d868525d2 glusterd: fix for remove-brick on just created/stopped volumes

in a fix to avoid race between stopping the brick and deleting
it in remove-brick (15396f490d23c665d51a64a049679cb40472ab05)
we moved delete of the brick inside stop volume, which was
totally inside the 'if (volinfo->status == STARTED)' section.
thus it made remove-brick of stopped/created volume as a failure.

Signed-off-by: Amar Tumballi <amarts@redhat.com>
BUG: 867252
Change-Id: Ie251e59a0b7ddb6965d8d48fb2a3bdb3bd11653d
Reviewed-on: http://review.gluster.org/4127
Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Tested-by: Jeff Darcy <jdarcy@redhat.com>

2012-10-24 09:49:30 -07:00

basic

tests: pre-commit regression tests

2012-10-18 14:17:25 -07:00

bugs

glusterd: fix for remove-brick on just created/stopped volumes

2012-10-24 09:49:30 -07:00

include.rc

tests: pre-commit regression tests

2012-10-18 14:17:25 -07:00

README

tests: pre-commit regression tests

2012-10-18 14:17:25 -07:00

README

How to use use
==============

- Build and install the version of glusterfs with your changes. Make
  sure the installed version is accessible from $PATH.

- (optional) Set environment variables to specify location of
  export directories and mount points. Unless you have special
  requirements, the defaults should just work. The variables
  themselves can be found at the top of tests/include.rc. All
  of them can be overriden with environment variables.

- Execute run-tests.sh in the top level directory as root.

- If some test cases fail, you can execute the failed test case script
  directly bypassing run-tests.sh. At this time it might be
  useful to set the envrionment variable DEBUG=1 before running
  the individual test script directly by hand.

- BE WARNED THAT THE TEST CASES DELETE /var/lib/glusterd/* !!!