From 2a46c8769bc2b6ad491a305ea1d38023d0e22617 Mon Sep 17 00:00:00 2001 From: Raghavendra Talur Date: Thu, 24 Jan 2013 11:26:37 +0530 Subject: cluster/dht: Correct min_free_disk behaviour Problem: Files were being created in subvol which had less than min_free_disk available even in the cases where other subvols with more space were available. Solution: Changed the logic to look for subvol which has more space available. In cases where all the subvols have lesser than Min_free_disk available , the one with max space and atleast one inode is available. Known Issue: Cannot ensure that first file that is created right after min-free-value is crossed on a brick will get created in other brick because disk usage stat takes some time to update in glusterprocess. Will fix that as part of another bug. Change-Id: If3ae0bf5a44f8739ce35b3ee3f191009ddd44455 BUG: 858488 Signed-off-by: Raghavendra Talur Reviewed-on: http://review.gluster.org/4420 Tested-by: Gluster Build System Reviewed-by: Anand Avati --- tests/include.rc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'tests/include.rc') diff --git a/tests/include.rc b/tests/include.rc index 1d1386f98..5d9c96cea 100644 --- a/tests/include.rc +++ b/tests/include.rc @@ -168,6 +168,21 @@ function cleanup() { killall -15 glusterfs glusterfsd glusterd 2>/dev/null || true; killall -9 glusterfs glusterfsd glusterd 2>/dev/null || true; + + MOUNTPOINTS=`mount | grep "$B0/" | awk '{print $3}'` + for m in $MOUNTPOINTS; + do + umount $m + done + + + LOOPDEVICES=`losetup -a | grep "$B0/" | awk '{print $1}' | tr -d :` + for l in $LOOPDEVICES; + do + losetup -d $l + done + + rm -rf /var/lib/glusterd/* $B0/* /etc/glusterd/*; umount -l $M0 2>/dev/null || true; -- cgit