Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1411613

Summary: Fix the place where graph switch event is logged
Product: [Community] GlusterFS Reporter: Krutika Dhananjay <kdhananj>
Component: fuseAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.8CC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1411612 Environment:
Last Closed: 2017-01-16 12:28:10 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: 1411612, 1411614    
Bug Blocks:    

Description Krutika Dhananjay 2017-01-10 06:26:02 UTC
+++ This bug was initially created as a clone of Bug #1411612 +++

Description of problem:
This should give more precise timestamp that indicates *exactly* when graph switch took place and hopefully help with some of the graph-switch related bugs that the users are reporting in future.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2017-01-10 01:23:18 EST ---

REVIEW: http://review.gluster.org/16365 (mount/fuse: Fix the place where graph-switch event is logged) posted (#1) for review on release-3.9 by Krutika Dhananjay (kdhananj)

Comment 1 Worker Ant 2017-01-10 06:26:57 UTC
REVIEW: http://review.gluster.org/16366 (mount/fuse: Fix the place where graph-switch event is logged) posted (#1) for review on release-3.8 by Krutika Dhananjay (kdhananj)

Comment 2 Worker Ant 2017-01-11 03:09:28 UTC
REVIEW: http://review.gluster.org/16366 (mount/fuse: Fix the place where graph-switch event is logged) posted (#2) for review on release-3.8 by Krutika Dhananjay (kdhananj)

Comment 3 Worker Ant 2017-01-11 08:39:38 UTC
COMMIT: http://review.gluster.org/16366 committed in release-3.8 by Niels de Vos (ndevos) 
------
commit bdb7f9d2c8fdca9c5874a2569250de7b6a68fa57
Author: Krutika Dhananjay <kdhananj>
Date:   Wed Dec 28 14:32:12 2016 +0530

    mount/fuse: Fix the place where graph-switch event is logged
    
            Backport of: http://review.gluster.org/16302
    
    fuse-bridge changes the active subvol in fuse_graph_sync(), and not in
    fuse_graph_setup(). This patch is written to get more accurate timestamp
    in the logs as to when a graph switch actually happened and in the hope
    that this will help better in identifying the issue of VM corruption
    that users are seeing when they add-bricks.
    
    Change-Id: I3c8577b87db02a2a6ce6159e7d04cf58a2bda0c1
    BUG: 1411613
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/16366
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 4 Niels de Vos 2017-01-16 12:28:10 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.8, please open a new bug report.

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