Bug 1406348 - [Eventing]: POSIX_SAME_GFID event seen for .trashcan folder and .trashcan/internal_op
Summary: [Eventing]: POSIX_SAME_GFID event seen for .trashcan folder and .trashcan/int...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: eventsapi
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Ashish Pandey
QA Contact:
URL:
Whiteboard:
Depends On: 1404110
Blocks: 1407014
TreeView+ depends on / blocked
 
Reported: 2016-12-20 10:45 UTC by Ashish Pandey
Modified: 2017-03-06 17:40 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.10.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1404110
: 1407014 (view as bug list)
Environment:
Last Closed: 2017-03-06 17:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2016-12-20 10:49:43 UTC
REVIEW: http://review.gluster.org/16212 (storage/posix: Do not create a directory which already exist) posted (#1) for review on master by Ashish Pandey (aspandey)

Comment 2 Worker Ant 2016-12-21 15:06:58 UTC
REVIEW: http://review.gluster.org/16212 (storage/posix: Do not create a directory which already exist) posted (#2) for review on master by Ashish Pandey (aspandey)

Comment 3 Worker Ant 2016-12-22 05:41:07 UTC
COMMIT: http://review.gluster.org/16212 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 97bfea234b1c097e7217181e7e6285fbd553d003
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>

Comment 4 Shyamsundar 2017-03-06 17:40:20 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.10.0, please open a new bug report.

glusterfs-3.10.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/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.