Bug 1002117

Summary:	quota build 3: mkdir and cp failed on a single brick volume
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Saurabh <saujain>
Component:	glusterd	Assignee:	Raghavendra G <rgowdapp>
Status:	CLOSED ERRATA	QA Contact:	Saurabh <saujain>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.1	CC:	grajaiya, mzywusko, rgowdapp, rhs-bugs, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.34rhs	Doc Type:	Bug Fix
Doc Text:	Cause: Before creating a file/directory or writing to a file, Quota enforcer requests Quota aggregator for the size of volume to make the decision whether to allow create/write operation. Quota aggregator takes a volume-id and a path and returns the size consumed by that path in the volume represented by volume-id. Because of a string comparison error, sometimes Quota aggregator would pick up a wrong volume and path wouldn't be valid in that volume. Consequence: Since path wouldn't be valid in the (wrong) volume picked up by Quota aggregator, query for size of the volume would fail and as a consequence Quota enforcer would fail writes/creates too. Fix: Make Quota aggregator pick correct volume based on the volume-id provided by Quota enforcer. Result:	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-27 15:35:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Saurabh 2013-08-28 13:27:18 UTC

Description of problem:

mkdir and cp on a volume with single brick, over nfs mount-point

Actually was having a volume with a name "dist1"
and one more volume with similar name "dist"
so as per discussion with developer that may be issue with string comparison

Version-Release number of selected component (if applicable):
glusterfs-fuse-3.4.0.20rhsquota5-1.el6rhs.x86_64
glusterfs-libs-3.4.0.20rhsquota5-1.el6rhs.x86_64
glusterfs-api-3.4.0.20rhsquota5-1.el6rhs.x86_64
glusterfs-geo-replication-3.4.0.20rhsquota5-1.el6rhs.x86_64
glusterfs-server-3.4.0.20rhsquota5-1.el6rhs.x86_64
glusterfs-3.4.0.20rhsquota5-1.el6rhs.x86_64
glusterfs-rdma-3.4.0.20rhsquota5-1.el6rhs.x86_64


How reproducible:
always

Expected results:
this should not be case, each volume should be considered a separate entity.

Additional info:

Comment 2 Raghavendra G 2013-08-29 16:37:08 UTC

Patch can be found at https://code.engineering.redhat.com/gerrit/12135

Comment 3 Saurabh 2013-10-22 06:32:50 UTC

working on glusterfs-3.4.0.35rhs

Comment 4 errata-xmlrpc 2013-11-27 15:35:20 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-1769.html