From 1e4a046828ea11cb4c7738a2a00fb715f84dc1ff Mon Sep 17 00:00:00 2001 From: Ravishankar N Date: Thu, 19 Jun 2014 17:41:25 +0000 Subject: cluster/stripe: don't treat ESTALE as failure in lookup Problem: In a stripe volume, symlinks are created only on the first brick via the default_symlink() call. During gfid lookup, server sends ESTALE from the other bricks, which is treated as error in stripe_lookup_cbk() Fix: Don't treat ESTALE as error in stripe_lookup_cbk() Change-Id: Ie4ac8f0dfd3e61260161620bdc53665882e7adbd BUG: 1111454 Signed-off-by: Ravishankar N Reviewed-on: http://review.gluster.org/8135 Reviewed-by: Raghavendra Bhat Tested-by: Gluster Build System Reviewed-by: Vijay Bellur --- tests/bugs/bug-1111454.t | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 tests/bugs/bug-1111454.t (limited to 'tests') diff --git a/tests/bugs/bug-1111454.t b/tests/bugs/bug-1111454.t new file mode 100644 index 0000000000..49f080d975 --- /dev/null +++ b/tests/bugs/bug-1111454.t @@ -0,0 +1,18 @@ +#!/bin/bash + +. $(dirname $0)/../include.rc +. $(dirname $0)/../volume.rc + +#symlink resolution should succeed +cleanup; + +TEST glusterd +TEST pidof glusterd +TEST $CLI volume create $V0 stripe 2 $H0:$B0/${V0}{0,1} +TEST $CLI volume start $V0 +TEST glusterfs --volfile-id=/$V0 --volfile-server=$H0 $M0 --attribute-timeout=0 --entry-timeout=0 +TEST mkdir $M0/dir +TEST touch $M0/dir/file +TEST ln -s file $M0/dir/symlinkfile +TEST ls -lR $M0 +cleanup -- cgit