glusterfs

History

Venky Shankar 19de18219b cluster/dht: pathinfo xattr changes for directories

Since directories have presence on all subvolumes there is
no definite meaning of ->hashed_subvol or ->cached_subvol.
getxattr() code path chooses ->cached_subvol for pathinfo
extended attribute. While this makes sense of files, it makes
less sense for directories. Further if a hashed or a cached
subvolume is down, and there's a getxattr request for a
directory, we return with an errno.

This patch changes pathinfo extended attribute contents by
aggregating information from all subvolumes that are up.

Change-Id: I58adb741d63ccfd1d0239af75eb65f26f0fb384d
Signed-off-by: Venky Shankar <vshankar@redhat.com>
BUG: 856455
Reviewed-on: http://review.gluster.org/4047
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Anand Avati <avati@redhat.com>

2013-02-08 19:09:46 -08:00

basic

Tests: Basic pump test case

2013-02-03 11:37:44 -08:00

bugs

cluster/dht: pathinfo xattr changes for directories

2013-02-08 19:09:46 -08:00

performance

open-behind: translator to perform open calls in background

2013-02-06 13:16:08 -08:00

utils

glusterd, cli: Task id's for async tasks

2012-12-19 13:32:49 -08:00

include.rc

cluster/dht: Correct min_free_disk behaviour

2013-02-04 08:43:50 -08:00

README

tests/README: add a note about usage of 'mount -t glusterfs'

2012-11-29 22:01:25 -08:00

volume.rc

Tests: Fixes to state-dump gen function

2013-02-08 11:40:03 -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/* !!!