Bug 1407014

Summary:	[Eventing]: POSIX_SAME_GFID event seen for .trashcan folder and .trashcan/internal_op
Product:	[Community] GlusterFS	Reporter:	Ashish Pandey <aspandey>
Component:	eventsapi	Assignee:	Ashish Pandey <aspandey>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.9	CC:	amukherj, pkarampu, rcyriac, sanandpa, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1406348	Environment:
Last Closed:	2017-03-08 08:43:57 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:	1404110, 1406348
Bug Blocks:

Comment 1 Worker Ant 2016-12-22 05:55:50 UTC

REVIEW: http://review.gluster.org/16267 (storage/posix: Do not create a directory which already exist) posted (#1) for review on release-3.9 by Ashish Pandey (aspandey)

Comment 2 Worker Ant 2017-01-12 06:22:15 UTC

COMMIT: http://review.gluster.org/16267 committed in release-3.9 by Pranith Kumar Karampuri (pkarampu) 
------
commit ac576a53877bdcfc3b80d08932deeea7dfe0eb32
Author: Ashish Pandey <aspandey>
Date:   Tue Dec 20 16:09:10 2016 +0530

    storage/posix: Do not create a directory which already exist
    
    Problem: While brick process starts, it tries to create trashcan
    and internal_op directory with fixed gfids. For the first time
    these directories will not be present. However, stop and start
    of volume again tries to create these directories, which are
    already present.
    This throws a gfid exist warning and EEXIST error in logs.
    
    Solution: Check if the directory exist on brick and gfid of
    this dir and the requested gfid matches or not.
    
    >Change-Id: Ie4966a550ed44046e0f2d10e9dbd540182ea97d2
    >BUG: 1406348
    >Signed-off-by: Ashish Pandey <aspandey>
    >Reviewed-on: http://review.gluster.org/16212
    >Smoke: Gluster Build System <jenkins.org>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    >Signed-off-by: Ashish Pandey <aspandey>
    
    Change-Id: Ie4966a550ed44046e0f2d10e9dbd540182ea97d2
    BUG: 1407014
    Signed-off-by: Ashish Pandey <aspandey>
    Reviewed-on: http://review.gluster.org/16267
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

Comment 3 Kaushal 2017-03-08 10:24:32 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.1, please open a new bug report.

glusterfs-3.9.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://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html
[2] https://www.gluster.org/pipermail/gluster-users/