glusterfs

History

shishir gowda 164c9586ae cluster/distribute: Preserve file size during rebalance migration If holes are encountered, then we do not write these to the dst, which sometimes causes file size to be lesser than src. Data is not corrupted, as when non-zero reads are received, we do write that data. Calling a truncrate to give file size to prevent it from being truncated to less than src in case the file end has holes. Thanks to Brian Foster for providing the test case Change-Id: I3cdd143b63ec8d797273d76189dff8b05eb9e551 BUG: 915554 Signed-off-by: shishir gowda <sgowda@redhat.com> Reviewed-on: http://review.gluster.org/4574 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@redhat.com>		2013-02-25 23:01:28 -08:00
..
basic	glusterfs.spec.in: resync with Fedora glusterfs.spec	2013-02-19 10:21:10 -08:00
bugs	cluster/distribute: Preserve file size during rebalance migration	2013-02-25 23:01:28 -08:00
performance	performance/open-behind: use anonymous fd for doing fstat and readv	2013-02-19 16:07:21 -08:00
utils	glusterd, cli: Task id's for async tasks	2012-12-19 13:32:49 -08:00
dht.rc	cluster/distribute: Preserve file size during rebalance migration	2013-02-25 23:01:28 -08:00
fileio.rc	tests/fileio.rc: library for file descriptor based IO in tests	2013-02-21 23:26:57 -08:00
include.rc	tests: move common funtion definitions to include.rc	2013-02-22 12:12:26 -08:00
README	tests/README: add a note about usage of 'mount -t glusterfs'	2012-11-29 22:01:25 -08:00
volume.rc	libglusterfs: Fix memory leaks in fd_lk_insert_and_merge	2013-02-17 17:03:40 -08:00

README

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/* !!!