Description of problem: Finding this issue of "Disk quota exceeded" for rename while trying to rename a file back to it's original name. Eg:- Say the quota is enabled and limits set on "/", say quota limit is set to some arbitrary number "100GB" create a file of size 5GB with the name of "5GB". Now, try to fill the "/" with data say upto 96 or 98GB. Try to rename the file from "5GB" to say "5GB-rename" again try to rename back to original name "5GB-rename" to "5GB" The second trial fails with "Disk quota exceeded" Version-Release number of selected component (if applicable): glusterfs-3.6.0.33-1.el6rhs.x86_64 How reproducible: sometimes Steps to Reproduce: 1. create a volume of 6x2 type, start it 2. enable quota 3. set a limit of 108GB on "/" 4. create a file of 5GB with name "5GB" afer mounting the volume over nfs 5. fill the volume till say 106 or 107 GB 6. try to rename the file "5GB" to "5GB-rename" 7. try to rename the file "5GB-rename" back to original name "5GB" Actual results: step6 rename is successful step7 rename is not successful, [root@rhsauto015 nfs-test]# mv 5GB-rename 5GB mv: cannot move `5GB-rename' to `5GB': Disk quota exceeded quota list, [root@nfs1 ~]# gluster volume quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 108.0GB 80% 107.0GB 1.0GB Yes No /dir1/dir5 25.0GB 80% 24.8GB 203.9MB Yes No brick logs reports this, [2014-11-25 05:15:57.889674] I [server-handshake.c:578:server_setvolume] 0-vol0-server: accepted client from nfs1-16813-2014/11/25-05:15:57:743662-vol0-client-10-0-0 (version: 3.6.0.33) [2014-11-25 05:57:13.579674] I [server-rpc-fops.c:964:server_rename_cbk] 0-vol0-server: 5507: RENAME /5GB-rename (00000000-0000-0000-0000-000000000000/5GB-rename) -> /5GB (00000000-0000-0000-0000-000000000000/5GB) ==> (Disk quota exceeded) [2014-11-25 05:57:56.295356] I [server-rpc-fops.c:964:server_rename_cbk] 0-vol0-server: 5552: RENAME /5GB-rename (00000000-0000-0000-0000-000000000000/5GB-rename) -> /5GB (00000000-0000-0000-0000-000000000000/5GB) ==> (Disk quota exceeded) [2014-11-25 06:04:39.233681] I [server-rpc-fops.c:964:server_rename_cbk] 0-vol0-server: 5566: RENAME /5GB-rename (00000000-0000-0000-0000-000000000000/5GB-rename) -> /5GB1 (00000000-0000-0000-0000-000000000000/5GB1) ==> (Disk quota exceeded) [2014-11-25 06:10:40.635836] I [server-rpc-fops.c:964:server_rename_cbk] 0-vol0-server: 5687: RENAME /5GB11111 (00000000-0000-0000-0000-000000000000/5GB11111) -> /5GB (00000000-0000-0000-0000-000000000000/5GB) ==> (Disk quota exceeded) [2014-11-25 06:11:12.831454] I [server-rpc-fops.c:964:server_rename_cbk] 0-vol0-server: 5706: RENAME /5GB11111 (00000000-0000-0000-0000-000000000000/5GB11111) -> /5GB (00000000-0000-0000-0000-000000000000/5GB) ==> (Disk quota exceeded) Expected results: rename to original name also should happen Additional info:
Created attachment 961009 [details] sosreport of node1
Created attachment 961010 [details] sosreport of node3
Patch https://code.engineering.redhat.com/gerrit/#/c/39200/ fixes the issue
on server, [root@vm1 ~]# gluster volume quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 100.0GB 80% 47.9GB 52.1GB No No /dir1 18.0GB 80% 17.0GB 1.0GB Yes No /dir2 22.9GB 80% 22.9GB 0Bytes Yes Yes on client, Change the filename mv 5GBfile 5GBfile-rename rename it back to original mv dirn1-rename/5GBfile-rename dirn1-rename/5GBfile ls -l dirn1-rename/5GBfile -rw-r--r--. 1 root root 5368709120 Mar 3 05:22 dirn1-rename/5GBfile Verified on glusterfs-3.6.0.48-1.el6rhs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0682.html