273a42a421
Problem: gfid-self-heal always assigns the gfid(GFID-1) it gets from lookup. Between the time of lookup to triggering the gfid-self-heal the entry could have changed. Now lets say there is a case where one of the files of the replica subolumes already has a gfid (GFID-2) and the other does not. In that case healing should happen with GFID-2 instead of GFID-1. Fix: Missing-entry-self-heal already handles all these cases. So removed separate handling of gfid-self-heal. Change-Id: Ie96261e9036c8f3cb4cad89347f9bf7b681cdc1a BUG: 767585 Signed-off-by: Pranith Kumar K <pkarampu@redhat.com> Reviewed-on: http://review.gluster.org/2670 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com> |
||
---|---|---|
.. | ||
basic | ||
bugs | ||
performance | ||
utils | ||
afr.rc | ||
cluster.rc | ||
dht.rc | ||
fileio.rc | ||
include.rc | ||
README | ||
volume.rc |
How to use test script framework. ================================= - Build and install the version of glusterfs with your changes. Make sure the installed version is accessible from $PATH. - To mount glusterfs, NEVER use 'mount -t glusterfs', instead use 'glusterfs -s ' method. This is because with the patch build setup doesnot install the /sbin/mount.glusterfs necessary, where as the glusterfs binary will be accessible with $PATH, and will pick the right version. - (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/* !!!