Bug 1250297 - [New] - glusterfs dead when user creates a rdma volume
Summary: [New] - glusterfs dead when user creates a rdma volume
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: rdma
Version: mainline
Hardware: All
OS: All
urgent
high
Target Milestone: ---
Assignee: Mohammed Rafi KC
QA Contact:
URL:
Whiteboard:
Depends On: 1250189
Blocks: 1254430
TreeView+ depends on / blocked
 
Reported: 2015-08-05 04:30 UTC by Mohammed Rafi KC
Modified: 2016-06-16 13:28 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1250189
: 1254430 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:28:57 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2015-08-05 06:48:14 UTC
REVIEW: http://review.gluster.org/11829 (rdma:restore device linked list structure in case of failure) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

Comment 2 Mohammed Rafi KC 2015-08-05 07:01:20 UTC
It is a race scenario where a device creation is failed and before properly cleaning up the failure, anoter operation started to act on it.

Comment 3 Anand Avati 2015-08-06 05:50:10 UTC
REVIEW: http://review.gluster.org/11829 (rdma:restore device linked list structure in case of failure) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

Comment 4 Anand Avati 2015-08-14 05:21:15 UTC
COMMIT: http://review.gluster.org/11829 committed in master by Raghavendra G (rgowdapp) 
------
commit 7641eb8b469a6dd4db6db59d2a5ef4d5a65e1a61
Author: Mohammed Rafi KC <rkavunga>
Date:   Wed Aug 5 12:07:48 2015 +0530

    rdma:restore device linked list structure in case of failure
    
    We maintain a linked list strcture to store device information,
    and maintain head in a ctx variable. A new device will be added
    at the beginning of list. But if the device creation failed, then
    we need to adjust the linked list to proper state.
    
    Change-Id: I07cefd3b808d8973a915728b3ba7f2955d29c92a
    BUG: 1250297
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/11829
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 5 Niels de Vos 2016-06-16 13:28:57 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.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[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.