Bug 1218031

Summary: GlusterD crashes on NetBSD when running mgmt_v3-locks.t test
Product: [Community] GlusterFS Reporter: Kaushal <kaushal>
Component: glusterdAssignee: Kaushal <kaushal>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: bugs, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://article.gmane.org/gmane.comp.file-systems.gluster.devel/10520/
Whiteboard:
Fixed In Version: glusterfs-3.7.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-14 17:29:34 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: 1205186    
Bug Blocks: 1199352    

Description Kaushal 2015-05-04 05:02:39 UTC
GlusterD crashed with a SIGILL when running the mgmt_v3-locks.t test during regression run.

More details can be about the crash can be found at http://article.gmane.org/gmane.comp.file-systems.gluster.devel/10520/

Comment 1 Kaushal 2015-05-04 05:04:26 UTC
Review posted for change at https://review.gluster.org/10426

Comment 2 Anand Avati 2015-05-06 06:33:28 UTC
REVIEW: http://review.gluster.org/10426 (glusterd: Use uint32_t for peerinfo generation number) posted (#4) for review on release-3.7 by Kaushal M (kaushal)

Comment 3 Anand Avati 2015-05-06 09:42:05 UTC
REVIEW: http://review.gluster.org/10426 (glusterd: Use uint32_t for peerinfo generation number) posted (#5) for review on release-3.7 by Vijay Bellur (vbellur)

Comment 4 Anand Avati 2015-05-06 17:47:29 UTC
COMMIT: http://review.gluster.org/10426 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 141ec83ea6e33934d029f030efab48f334a78d72
Author: Kaushal M <kaushal>
Date:   Tue Apr 28 18:42:41 2015 +0530

    glusterd: Use uint32_t for peerinfo generation number
    
    Using a uint64_t for the peerinfo generation number was overkill for how
    the generation number is used within GlusterD. It also prevented
    GlusterD from running on 32-bit architechtures, as uatomic_add_return
    doesn't support 64-bit values on 32-bit architechtures.
    
    This change was developed on the git branch at [1]. This commit is a
    combination of the following commits on the development branch.
      b78dba4 Use 32-bit generation number
      2c37e4b Change other generation number variables to uint32_t
    
    [1]: https://github.com/kshlm/glusterfs/tree/urcu
    
    Change-Id: I0f310f56a4fb97d6bcbc23255a379ed5bb1ed9e1
    BUG: 1218031
    Signed-off-by: Kaushal M <kaushal>
    Reviewed-on: http://review.gluster.org/10426
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 5 Niels de Vos 2015-05-14 17:29:34 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.0, please open a new bug report.

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

Comment 6 Niels de Vos 2015-05-14 17:35:58 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.0, please open a new bug report.

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

Comment 7 Niels de Vos 2015-05-14 17:38:19 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.0, please open a new bug report.

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

Comment 8 Niels de Vos 2015-05-14 17:47:12 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.0, please open a new bug report.

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