Description of problem: executing rm -rf * on the mount point, error messages are found in quotad.log Version-Release number of selected component (if applicable): [root@quota1 ~]# rpm -qa | grep glusterfs glusterfs-fuse-3.4.0.12rhs.beta2-1.el6rhs.x86_64 glusterfs-server-3.4.0.12rhs.beta2-1.el6rhs.x86_64 glusterfs-debuginfo-3.4.0.12rhs.beta2-1.el6rhs.x86_64 glusterfs-3.4.0.12rhs.beta2-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. create a volume, start it 2. enable quota and set some limit on the root of the volume 3. mount the volume using nfs 4. create 500 dirs 5. one single sub dir in each of the above created dir 6. set limit for dirs as 2GB 7. set limit for subdir as 1GB 8. rm -rf * on mount point Actual results: [2013-07-05 05:49:26.562939] E [quotad.c:501:qd_handle_entry] 0-dist-rep: Quota check on (null) failed [2013-07-05 05:49:26.565226] W [inode.c:935:inode_forget] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_handle_entry+0x13d) [0x7f01e6180a2d] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_entry+0x309) [0x7f01e6180889] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_handle_error+0x72) [0x7f01e617f492]))) 0-quotad: inode not found [2013-07-05 05:49:26.565252] E [quotad.c:501:qd_handle_entry] 0-dist-rep: Quota check on (null) failed [2013-07-05 05:49:26.567526] W [inode.c:935:inode_forget] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_handle_entry+0x13d) [0x7f01e6180a2d] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_entry+0x309) [0x7f01e6180889] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_handle_error+0x72) [0x7f01e617f492]))) 0-quotad: inode not found [2013-07-05 05:49:26.567542] E [quotad.c:501:qd_handle_entry] 0-dist-rep: Quota check on (null) failed [2013-07-05 05:49:26.586597] E [quotad.c:501:qd_handle_entry] 0-dist-rep: Quota check on (null) failed [2013-07-05 05:49:26.590244] W [inode.c:935:inode_forget] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_handle_entry+0x13d) [0x7f01e6180a2d] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_entry+0x309) [0x7f01e6180889] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_handle_error+0x72) [0x7f01e617f492]))) 0-quotad: inode not found [2013-07-05 05:49:26.590263] E [quotad.c:501:qd_handle_entry] 0-dist-rep: Quota check on (null) failed [2013-07-05 05:49:26.593530] W [inode.c:935:inode_forget] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_handle_entry+0x13d) [0x7f01e6180a2d] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_entry+0x309) [0x7f01e6180889] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_handle_error+0x72) [0x7f01e617f492]))) 0-quotad: inode not found [2013-07-05 05:49:26.593548] E [quotad.c:501:qd_handle_entry] 0-dist-rep: Quota check on (null) failed [2013-07-05 05:49:26.596221] W [inode.c:935:inode_forget] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_handle_entry+0x13d) [0x7f01e6180a2d] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_entry+0x309) [0x7f01e6180889] (-->/usr/lib64/glusterfs/3.4.0.12rhs.beta2/xlator/features/quotad.so(qd_resolve_handle_error+0x72) [0x7f01e617f492]))) 0-quotad: inode not found [2013-07-05 05:49:26.596235] E [quotad.c:501:qd_handle_entry] 0-dist-rep: Quota check on (null) failed [2013-07-05 05:49:26.596301] W [dht-layout.c:179:dht_layout_search] 0-dist-rep: no subvolume for hash (value) = 2221416999 ^C Expected results: it is just a delettion of the data, why does quotad crib? expected it quotad shouldn't be doing quota check during deletion of data. Additional info: BZ 981653 BZ 981661 were filed before this bug.
Varun, this has potential to de-rail the debugging session. Can you please check and fix it?
CHANGE: https://code.engineering.redhat.com/gerrit/9436 fixes the issue.
Since the implementation changed, can you verify with v3.4.0qa8?