Bug 1347590

Summary:	Ganesha+Tiering: Continuous "0-glfs_h_poll_cache_invalidation: invalid argument" messages getting logged in ganesha-gfapi logs.
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	ganesha-nfs	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.8.0	CC:	bugs, jthottan, kkeithle, ndevos, nlevinki, rhs-bugs, skoduri, sraj, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1331969	Environment:
Last Closed:	2016-07-08 14:43:58 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:	1331969
Bug Blocks:	1323424, 1332433

Comment 1 Vijay Bellur 2016-06-17 09:06:42 UTC

REVIEW: http://review.gluster.org/14756 (gfapi/upcall: Ignore handle create failures) posted (#1) for review on release-3.8 by soumya k (skoduri)

Comment 2 Vijay Bellur 2016-06-17 12:25:34 UTC

COMMIT: http://review.gluster.org/14756 committed in release-3.8 by Kaleb KEITHLEY (kkeithle) 
------
commit ae47d5b55e5c5f32a45bd9d1dd741a1c072ab2d6
Author: Soumya Koduri <skoduri>
Date:   Sat Apr 30 22:01:47 2016 +0530

    gfapi/upcall: Ignore handle create failures
    
    In "glfs_h_poll_cache_invalidation", we need to send upcall only if there
    is a corresponding inode entry in the gfapi inode table for that handle.
    
    That's because the application will have reference to the inode as long as
    it operates on any handle. That means the only case in which we cannot find
    inode is when the application has closed the handle (either as part of unlink
    or for any other purpose). But since it will have no more references and will
    not be interested in any upcall event for that handle, we can safely ignore such
    cases.
    
    Note: This will affect only that particular applicaiton process/local libgfapi
    client.
    
    This is backport of below mainline patch -
       http://review.gluster.org/14132
    
    Change-Id: I9499cd9c284350d4a271e58f2a0966db65a7a61c
    BUG: 1347590
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/14132
    Reviewed-by: jiffin tony Thottan <jthottan>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    (cherry picked from commit fb77938fc7810dc5ac16b0de9694157cde93635e)
    Reviewed-on: http://review.gluster.org/14756
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Niels de Vos 2016-07-08 14:43:58 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.8.1, please open a new bug report.

glusterfs-3.8.1 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://thread.gmane.org/gmane.comp.file-systems.gluster.packaging/156
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user