Bug 1357463

Summary:	Error: quota context not set inode (gfid:nnn) [Invalid argument]
Product:	[Community] GlusterFS	Reporter:	Manikandan <mselvaga>
Component:	quota	Assignee:	Raghavendra G <rgowdapp>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bkunal, bugs, ccalhoun, smohan, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1352125	Environment:
Last Closed:	2017-03-27 18:22:15 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:
Bug Depends On:
Bug Blocks:	1352125, 1368927

Comment 1 Vijay Bellur 2016-07-18 09:54:34 UTC

REVIEW: http://review.gluster.org/14940 (quota:  change the log level from warning to info) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 2 Vijay Bellur 2016-08-10 19:13:58 UTC

REVIEW: http://review.gluster.org/14940 (quota:  change the log level from warning to info) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)

Comment 3 Vijay Bellur 2016-08-17 16:53:11 UTC

COMMIT: http://review.gluster.org/14940 committed in master by Jeff Darcy (jdarcy) 
------
commit 4b01d6ea8da137f23a4372df35fcbd5dbec21d09
Author: Manikandan Selvaganesh <mselvaga>
Date:   Mon Jul 18 15:17:49 2016 +0530

    quota:  change the log level from warning to info
    
    Change-Id: Icac7d87bb6c5ecc813528690e03c821bbe3789b5
    BUG: 1357463
    Signed-off-by: Manikandan Selvaganesh <mselvaga>
    Reviewed-on: http://review.gluster.org/14940
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Prashanth Pai <ppai>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 6 Shyamsundar 2017-03-27 18:22:15 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report.

glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/