Hide Forgot
Description of problem: When we have reached the quota limit opening a file in Vi editor and appending the data violates the quota limits and data will be successfully written to the file. Version-Release number of selected component (if applicable): 3.4.0.36rhs-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1.created a 6x2 distributed replicate volume 2. create some files on the mount point using dd till we reach the quota limit (make sure that not even a single byte is left to fill up quota , which makes sure that even writing a single character to file violates quota) 3. to make sure that we have reached the quota limit try to append from the shell , say echo "hello" >> file , this should fail in appending data. 4.now open any file in Vi and append some data towards the end of the file 5. save and quit Actual results: data will be successfully written to the file there by violating quota limits Expected results: Additional info:
I see ""shanks.txt" E212: Can't open file for writing" when disk quota is already exceeded in a directory and you try to write a file using vim. I also happened to see: [shanks@localhost Music]$ vim shanks.txt E72: Close error on swap file [shanks@localhost Music]$ Needs further testing.
[root@vm1 home]# gluster volume quota test1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 100.0KB 80% 1.7MB 0Bytes Yes Yes I tried similar steps. After quota limit is reached tried to edit and save the file in vim and got the following error message while saving "file1" E512: Close failed WARNING: Original file may be lost or damaged do not quit the editor until the file is successfully written! Press ENTER or type command to continue
This needs to be documented: When the quota hard-timeout is set to default value of 30, the quota limit is checked once in 30 seconds and during that 30 second time window there is possibility of quota hard-limit being exceeded. In order to attain a strict checking of quota limit it is recommended to set the quota soft-timeout and hard-timeout to lower value so that quota limit is checked frequently, and possibility of quota hard-limit being exceeded is reduced.