Bug 823790

Summary: Renaming file says "Disk quota limit exceeded" even it has not.
Product: [Community] GlusterFS Reporter: shylesh <shmohan>
Component: quotaAssignee: Nagaprasad Sathyanarayana <nsathyan>
Status: CLOSED EOL QA Contact:
Severity: urgent Docs Contact:
Priority: medium    
Version: pre-releaseCC: bugs, divya, gluster-bugs, rwheeler, smohan, vmallika
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-22 08:45:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: DP CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description shylesh 2012-05-22 07:32:20 UTC
Description of problem:
Renaming a file whose size is greater than half of quota limit-usage set throws an error message saying "Disk quota limit exceeded"

Version-Release number of selected component (if applicable):
3.3.0qa42

How reproducible:


Steps to Reproduce:
1. Create a volume say distributed-replicate.
2. set quota limit of 900MB
3. Create a file of size 500MB say FILE1
4. Now rename FILE1 to something else.
  
Actual results:
An error message saying "Disk quota limit exceeded" will be displayed even though it has not.


Expected results:


Additional info:

Comment 1 Amar Tumballi 2012-07-11 11:12:00 UTC
Need to cross check if its properly documented. 
Divya, want your feedback here. If documented, can close it.

Comment 2 Divya 2012-07-11 12:32:20 UTC
This information is added as Known Issue in RHS 2.0 Release Notes and it is available at: http://docs.redhat.com/docs/en-US/Red_Hat_Storage/2.0/html/2.0_Release_Notes/chap-2.0_Release_Notes-Test_Chapter.html

Comment 3 Vidya Sakar 2012-08-15 01:54:21 UTC
(In reply to comment #2)
Divya, I suggest that this should be documented in the quota chapter of administration guide. While it is ok to document it as a known issue, this is also how it is expected to work, so admin guide documentation will be good. Moving the bug to DP.

Comment 5 Vijaikumar Mallikarjuna 2015-01-22 08:45:18 UTC
Closing the bug as 3.3 is not supported