Bug 764419 (GLUSTER-2687)

Summary:	Quota:after edit file not getting saved properly
Product:	[Community] GlusterFS	Reporter:	Saurabh <saurabh>
Component:	quota	Assignee:	Junaid <junaid>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	gluster-bugs, raghavendra, vagarwal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Saurabh 2011-04-07 12:03:16 UTC

with a distribute volume,

over nfs/fuse mount with quota enabled and limit set on the volume,

then on the client if you try edit a file, 

after saving it gives this problem


[root@centos-qa-client-1 nfs-test]# vi file
E72: Close error on swap file[root@centos-qa-client-1 nfs-test]# ls -li
total 20
11118338982438538141 drwxr-xr-x 2 root root 4096 Apr  7 02:29 d1
10058334542165874308 -rw-r--r-- 1 root root 6222 Apr  7 02:32 file
[root@centos-qa-client-1 nfs-test]#

Comment 1 Raghavendra G 2011-04-13 08:29:44 UTC

This issue is no longer seen in latest qa releases (qa11). On the other hand error in close is not invalid, since with write-behind loaded on top of quota, some writes that would've not permitted due to exceeding of quota would be cached by write-behind and sent later. Errors returned by quota for these writes can be returned by write-behind to application in subsequent fops and close can be one of these fops.