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

Bug 978794

Summary: [RHEV-RHS] Client crashed on hypervisor after rebalance on a distributed-replicate volume
Product: [Community] GlusterFS Reporter: Pranith Kumar K <pkarampu>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: mainlineCC: amarts, gluster-bugs, pkarampu, rhs-bugs, sasundar, shmohan, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 960899
: 978802 986158 (view as bug list) Environment:
virt rhev integration
Last Closed: 2013-07-24 18:02:13 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: 960899    
Bug Blocks: 978802, 986158    

Comment 1 Anand Avati 2013-06-27 07:31:43 UTC 
REVIEW: http://review.gluster.org/5258 (cluster/afr: Handle NULL fdctx in fsync) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
Comment 2 Anand Avati 2013-06-27 08:33:45 UTC 
REVIEW: http://review.gluster.org/5258 (cluster/afr: Handle NULL fdctx in fsync) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)
Comment 3 Anand Avati 2013-06-28 03:49:15 UTC 
REVIEW: http://review.gluster.org/5258 (cluster/afr: Handle NULL fdctx in fsync) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
Comment 4 Anand Avati 2013-06-28 06:35:04 UTC 
COMMIT: http://review.gluster.org/5258 committed in master by Vijay Bellur (vbellur) 
------
commit 0c05cde4a16c426089933803d082183227422307
Author: Pranith Kumar K <pkarampu>
Date:   Thu Jun 27 12:59:14 2013 +0530

    cluster/afr: Handle NULL fdctx in fsync
    
    Problem:
    If fdctx is NULL in afr_fsync, process crashes because
    of NULL dereference.
    
    Fix:
    if fdctx is NULL, always say witnessed unstable write so
    that fsyncs are done properly. Handled fdctx being null
    in afr_delayed_changelog_post_op otherwise fsync stub is
    never resumed and the mount was hanging.
    
    Change-Id: Icacc900e9be63c29db3325cb0e19cc250adebaac
    BUG: 978794
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/5258
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>