Bug 1243648 - Disperse volume: NFS crashed
Summary: Disperse volume: NFS crashed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: 3.7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On: 1240284
Blocks: 1223636 1240245
TreeView+ depends on / blocked
 
Reported: 2015-07-16 02:49 UTC by Pranith Kumar K
Modified: 2015-07-30 09:47 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.7.3
Clone Of: 1240284
Environment:
Last Closed: 2015-07-30 09:47:42 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Pranith Kumar K 2015-07-16 02:49:43 UTC
========
[2015-07-06 07:45:23.832283] A [MSGID: 0] [mem-pool.c:120:__gf_calloc] : no memory available for size (34917844374315) [call stack follows]
/usr/lib64/libglusterfs.so.0(_gf_msg_backtrace_nomem+0xb6)[0x7f07d7bed826]
/usr/lib64/libglusterfs.so.0(_gf_msg_nomem+0x370)[0x7f07d7bee530]
/usr/lib64/libglusterfs.so.0(__gf_calloc+0x139)[0x7f07d7c24959]
/usr/lib64/libglusterfs.so.0(iobuf_get_from_stdalloc+0x6e)[0x7f07d7c2633e]
/usr/lib64/libglusterfs.so.0(iobuf_get2+0xa3)[0x7f07d7c278e3]
[2015-07-06 07:45:23.842655] E [ec-common.c:259:ec_check_complete] (--> 0-: Assertion failed: fop->resume == NULL
[2015-07-06 07:45:23.842749] E [ec-common.c:259:ec_check_complete] (--> 0-: Assertion failed: fop->resume == NULL
[2015-07-06 07:45:23.842813] W [MSGID: 112018] [nfs3.c:2454:nfs3svc_create_setattr_cbk] 0-nfs: 66e8714c: <gfid:13a56d81-6d50-447c-9efc-619fa8140be4>/linux-4.0.1/arch/ia64/include/uapi/asm/setup.h => -1 (Input/output error) [Input/output error]
[2015-07-06 07:45:23.842860] W [MSGID: 112199] [nfs3-helpers.c:3496:nfs3_log_newfh_res] 0-nfs-nfsv3: XID: 66e8714c, CREATE: NFS: 5(I/O error), POSIX: 5(Input/output error), FH: exportid e852b17e-c253-42a6-ba84-ff16b6faa2c5, gfid 3982d8b1-f4a0-4010-9866-965c55813d76, mountid d8655fd7-0000-0000-0000-000000000000
[2015-07-06 07:45:23.842770] W [MSGID: 122040] [ec-common.c:895:ec_prepare_update_cbk] 0-vol3-disperse-0: Failed to get size and version [Input/output error]
[2015-07-06 07:45:23.843047] E [ec-generic.c:1362:ec_xattrop_cbk] (--> 0-vol3-disperse-0: invalid argument: frame->local [Invalid argument]
[2015-07-06 07:45:23.843619] W [MSGID: 122056] [ec-combine.c:888:ec_combine_check] 0-vol3-disperse-0: Mismatching xdata in

Comment 2 Anand Avati 2015-07-16 03:27:08 UTC
REVIEW: http://review.gluster.org/11683 (cluster/ec: Fix use after free bug) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 3 Anand Avati 2015-07-21 11:56:06 UTC
REVIEW: http://review.gluster.org/11683 (cluster/ec: Fix use after free bug) posted (#2) for review on release-3.7 by Xavier Hernandez (xhernandez)

Comment 4 Anand Avati 2015-07-21 21:43:13 UTC
COMMIT: http://review.gluster.org/11683 committed in release-3.7 by Xavier Hernandez (xhernandez) 
------
commit bdb3591ba86333639c7c604d0f984006e5b8a1de
Author: Pranith Kumar K <pkarampu>
Date:   Tue Jul 7 12:40:42 2015 +0530

    cluster/ec: Fix use after free bug
    
    In ec_lock() there is a chance that ec_resume is called on fop even before
    ec_sleep.  This can result in refs == 0 for fop leading to use after free in
    this function when it calls ec_sleep so do ec_sleep at start and ec_resume at
    end of this function.
    
     >Change-Id: I879b2667bf71eaa56be1b53b5bdc91b7bb56c650
     >BUG: 1240284
     >Signed-off-by: Pranith Kumar K <pkarampu>
     >Reviewed-on: http://review.gluster.org/11558
     >Reviewed-by: Xavier Hernandez <xhernandez>
     >Tested-by: Gluster Build System <jenkins.com>
     >Tested-by: NetBSD Build System <jenkins.org>
    
    BUG: 1243648
    Change-Id: I57515d1f478b2a41a20d37368c947049d23778f0
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/11683
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Xavier Hernandez <xhernandez>

Comment 5 Kaushal 2015-07-30 09:47:42 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.7.3, please open a new bug report.

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


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