I was able to sort out the issue after going through qa build script.
Ran the same steps as in the quota-rename.t (manually though. multiple times!), Could not reproduce the issue.
bash-4.3# bash -x /tmp/test_sku2
+ /build/install/sbin/gluster v create v1 nbslave71.cloud.gluster.org:/d/backends/ force
volume create: v1: success: please start the volume to access data
+ /build/install/sbin/gluster v start v1
volume start: v1: success
+ /build/install/sbin/gluster v quota v1 enable
volume quota : success
+ /build/install/sbin/glusterfs --volfile-id=v1 --volfile-server=nbslave71.cloud.gluster.org /glust_vol/
+ /build/install/sbin/gluster volume quota v1 hard-timeout 0
volume quota : success
+ /build/install/sbin/gluster volume quota v1 soft-timeout 0
volume quota : success
+ mkdir -p /glust_vol/dir/dir1
+ /build/install/sbin/gluster volume quota v1 limit-objects /dir 20
volume quota : success
+ mkdir /glust_vol/dir/dir1/d1 /glust_vol/dir/dir1/d2 /glust_vol/dir/dir1/d3 /glust_vol/dir/dir1/d4 /glust_vol/dir/dir1/d5
+ touch /glust_vol/dir/dir1/f1 /glust_vol/dir/dir1/f2 /glust_vol/dir/dir1/f3 /glust_vol/dir/dir1/f4 /glust_vol/dir/dir1/f5
+ mv /glust_vol/dir/dir1 /glust_vol/dir/dir2
+ /build/install/sbin/gluster v stop v1
+ yes
Stopping volume will make its data inaccessible. Do you want to continue? (y/n) volume stop: v1: success
+ yes
+ /build/install/sbin/gluster v delete v1
Deleting volume will erase all information about the volume. Do you want to continue? (y/n) volume delete: v1: success
+ rm -rf /glust_vol
bash-4.3#
bash-4.3#
bash-4.3# hostname
nbslave71.cloud.gluster.org
bash-4.3# uname -a
NetBSD nbslave71.cloud.gluster.org 7.0_STABLE NetBSD 7.0_STABLE (XEN3PAE_DOMU.201601291840Z) i386
Ran the same steps as in the quota-rename.t (manually though. multiple times!), Could not reproduce the issue.
bash-4.3# bash -x /tmp/test_sku2
+ /build/install/sbin/gluster v create v1 nbslave71.cloud.gluster.org:/d/backends/ force
volume create: v1: success: please start the volume to access data
+ /build/install/sbin/gluster v start v1
volume start: v1: success
+ /build/install/sbin/gluster v quota v1 enable
volume quota : success
+ /build/install/sbin/glusterfs --volfile-id=v1 --volfile-server=nbslave71.cloud.gluster.org /glust_vol/
+ /build/install/sbin/gluster volume quota v1 hard-timeout 0
volume quota : success
+ /build/install/sbin/gluster volume quota v1 soft-timeout 0
volume quota : success
+ mkdir -p /glust_vol/dir/dir1
+ /build/install/sbin/gluster volume quota v1 limit-objects /dir 20
volume quota : success
+ mkdir /glust_vol/dir/dir1/d1 /glust_vol/dir/dir1/d2 /glust_vol/dir/dir1/d3 /glust_vol/dir/dir1/d4 /glust_vol/dir/dir1/d5
+ touch /glust_vol/dir/dir1/f1 /glust_vol/dir/dir1/f2 /glust_vol/dir/dir1/f3 /glust_vol/dir/dir1/f4 /glust_vol/dir/dir1/f5
+ mv /glust_vol/dir/dir1 /glust_vol/dir/dir2
+ /build/install/sbin/gluster v stop v1
+ yes
Stopping volume will make its data inaccessible. Do you want to continue? (y/n) volume stop: v1: success
+ yes
+ /build/install/sbin/gluster v delete v1
Deleting volume will erase all information about the volume. Do you want to continue? (y/n) volume delete: v1: success
+ rm -rf /glust_vol
bash-4.3#
bash-4.3#
bash-4.3# hostname
nbslave71.cloud.gluster.org
bash-4.3# uname -a
NetBSD nbslave71.cloud.gluster.org 7.0_STABLE NetBSD 7.0_STABLE (XEN3PAE_DOMU.201601291840Z) i386
Thanks and Regards,
Sanoj
On Wed, Oct 26, 2016 at 11:48 AM, Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote:
Vijay Bellur <vbellur@xxxxxxxxxx> wrote:
> Emmanuel might be able to help with problems related to NetBSD
> environment.
Sure, feel free to ask if you hit NetBSD-speciic troubles.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@xxxxxxxxxx
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
