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

Bug 1230026

Summary: BVT: glusterd crashed and dumped during upgrade (on rhel7.1 server)
Product: [Community] GlusterFS Reporter: Anand Nekkunti <anekkunt>
Component: glusterdAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 3.7.0CC: akhakhar, amukherj, anekkunt, bugs, gluster-bugs, kripper, nsathyan, sasundar, vbellur
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.7.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1209461 Environment:
Last Closed: 2015-06-20 09:50:28 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: 1209461, 1230195    
Bug Blocks:    

Description Anand Nekkunti 2015-06-10 07:05:19 UTC
+++ This bug was initially created as a clone of Bug #1209461 +++

Description of problem:
glusterd has crashed and dumped core.
Core was generated by `glusterd --xlator-option *.upgrade=on -N'
backtrace of the core:

(gdb) bt
#0  0x00007f5cacc66c3b in rcu_bp_register () from /lib64/liburcu-bp.so.1
#1  0x00007f5cacc66f7e in rcu_read_lock_bp () from /lib64/liburcu-bp.so.1
#2  0x00007f5cad52d5d6 in __glusterd_peer_rpc_notify (rpc=rpc@entry=0x7f5cba0a17a0, mydata=mydata@entry=0x7f5cba0964a0, event=event@entry=RPC_CLNT_CONNECT, data=data@entry=0x0) at glusterd-handler.c:4681
#3  0x00007f5cad5250ec in glusterd_big_locked_notify (rpc=0x7f5cba0a17a0, mydata=0x7f5cba0964a0, event=RPC_CLNT_CONNECT, data=0x0, notify_fn=0x7f5cad52d580 <__glusterd_peer_rpc_notify>) at glusterd-handler.c:71
#4  0x00007f5cb827e610 in rpc_clnt_notify (trans=<optimized out>, mydata=0x7f5cba0a17d0, event=<optimized out>, data=<optimized out>) at rpc-clnt.c:926
#5  0x00007f5cb827a4c3 in rpc_transport_notify (this=this@entry=0x7f5cba0a4930, event=event@entry=RPC_TRANSPORT_CONNECT, data=data@entry=0x7f5cba0a4930) at rpc-transport.c:543
#6  0x00007f5caad75a27 in socket_connect_finish (this=this@entry=0x7f5cba0a4930) at socket.c:2366
#7  0x00007f5caad7af7f in socket_event_handler (fd=fd@entry=11, idx=idx@entry=2, data=0x7f5cba0a4930, poll_in=0, poll_out=4, poll_err=0) at socket.c:2396
#8  0x00007f5cb8504c1a in event_dispatch_epoll_handler (event=0x7f5ca8db1ec0, event_pool=0x7f5cba033c50) at event-epoll.c:572
#9  event_dispatch_epoll_worker (data=0x7f5cba0425b0) at event-epoll.c:674
#10 0x00007f5cb781fdf5 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f5cb71661ad in clone () from /lib64/libc.so.6


Version-Release number of selected component (if applicable):
Upstream glusterfs3.7 on Rhel7.1 server

How reproducible:


Steps to Reproduce:
1. Not a manual process
2. Running BVT on rhel7.1 server with upstream glusterfs3.7 packages
3. Recieved a core from one of the servers, when fssanity tests failed after watchdog timeout.


Actual results:


Expected results: Server not to crash.


Additional info:

--- Additional comment from Apeksha on 2015-04-07 08:32:24 EDT ---

sosreports and logs can be found in the following location;

http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1209461/

--- Additional comment from SATHEESARAN on 2015-04-07 11:29:17 EDT ---

(In reply to Apeksha from comment #1)
> sosreports and logs can be found in the following location;
> 
> http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1209461/

Apeksha,

The sosreports doesn't have permission to download.
Could you provide suitable perms to make it accessible ?

--- Additional comment from Apeksha on 2015-04-08 01:23:22 EDT ---

Changed the permissions. You will now be able to access the reports.

--- Additional comment from Kaushal on 2015-04-08 05:55:59 EDT ---

The crash is caused due to race between exit and a socket event.
```
(gdb) thr a a bt

Thread 7 (Thread 0x7f5ca95b3700 (LWP 13303)):
#0  0x00007f5cb7823705 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f5cad5af353 in hooks_worker (args=<optimized out>) at glusterd-hooks.c:501
#2  0x00007f5cb781fdf5 in start_thread () from /lib64/libpthread.so.0
#3  0x00007f5cb71661ad in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f5caf040700 (LWP 13151)):
#0  0x00007f5cab879859 in __do_global_dtors_aux () from /lib64/libselinux.so.1
#1  0x00007f5cb8744b5a in _dl_fini () from /lib64/ld-linux-x86-64.so.2
#2  0x00007f5cb70a8e49 in __run_exit_handlers () from /lib64/libc.so.6
#3  0x00007f5cb70a8e95 in exit () from /lib64/libc.so.6
#4  0x00007f5cb896253a in cleanup_and_exit (signum=<optimized out>) at glusterfsd.c:1242
#5  0x00007f5cb8962625 in glusterfs_sigwaiter (arg=<optimized out>) at glusterfsd.c:1983
#6  0x00007f5cb781fdf5 in start_thread () from /lib64/libpthread.so.0
#7  0x00007f5cb71661ad in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f5caf841700 (LWP 13150)):
#0  0x00007f5cb782699d in nanosleep () from /lib64/libpthread.so.0
#1  0x00007f5cb84c7224 in gf_timer_proc (ctx=0x7f5cba015010) at timer.c:191
#2  0x00007f5cb781fdf5 in start_thread () from /lib64/libpthread.so.0
#3  0x00007f5cb71661ad in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f5cae83f700 (LWP 13152)):
#0  0x00007f5cb7823ab2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f5cb84e9028 in syncenv_task (proc=proc@entry=0x7f5cba042a20) at syncop.c:591
#2  0x00007f5cb84e9c90 in syncenv_processor (thdata=0x7f5cba042a20) at syncop.c:683
#3  0x00007f5cb781fdf5 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f5cb71661ad in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f5cae03e700 (LWP 13153)):
#0  0x00007f5cb7823ab2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f5cb84e9028 in syncenv_task (proc=proc@entry=0x7f5cba042de0) at syncop.c:591
#2  0x00007f5cb84e9c90 in syncenv_processor (thdata=0x7f5cba042de0) at syncop.c:683
#3  0x00007f5cb781fdf5 in start_thread () from /lib64/libpthread.so.0
#4  0x00007f5cb71661ad in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f5cb8946740 (LWP 13149)):
#0  0x00007f5cb7820f27 in pthread_join () from /lib64/libpthread.so.0
#1  0x00007f5cb8504f25 in event_dispatch_epoll (event_pool=0x7f5cba033c50) at event-epoll.c:759
#2  0x00007f5cb895f61a in main (argc=4, argv=0x7fff8e7dc2b8) at glusterfsd.c:2313

Thread 1 (Thread 0x7f5ca8db2700 (LWP 13304)):
#0  0x00007f5cacc66c3b in rcu_bp_register () from /lib64/liburcu-bp.so.1
#1  0x00007f5cacc66f7e in rcu_read_lock_bp () from /lib64/liburcu-bp.so.1
#2  0x00007f5cad52d5d6 in __glusterd_peer_rpc_notify (rpc=rpc@entry=0x7f5cba0a17a0, mydata=mydata@entry=0x7f5cba0964a0, event=event@entry=RPC_CLNT_CONNECT, data=data@entry=0x0) at glusterd-handler.c:4681
#3  0x00007f5cad5250ec in glusterd_big_locked_notify (rpc=0x7f5cba0a17a0, mydata=0x7f5cba0964a0, event=RPC_CLNT_CONNECT, data=0x0, notify_fn=0x7f5cad52d580 <__glusterd_peer_rpc_notify>) at glusterd-handler.c:71
#4  0x00007f5cb827e610 in rpc_clnt_notify (trans=<optimized out>, mydata=0x7f5cba0a17d0, event=<optimized out>, data=<optimized out>) at rpc-clnt.c:926
#5  0x00007f5cb827a4c3 in rpc_transport_notify (this=this@entry=0x7f5cba0a4930, event=event@entry=RPC_TRANSPORT_CONNECT, data=data@entry=0x7f5cba0a4930) at rpc-transport.c:543
#6  0x00007f5caad75a27 in socket_connect_finish (this=this@entry=0x7f5cba0a4930) at socket.c:2366
#7  0x00007f5caad7af7f in socket_event_handler (fd=fd@entry=11, idx=idx@entry=2, data=0x7f5cba0a4930, poll_in=0, poll_out=4, poll_err=0) at socket.c:2396
#8  0x00007f5cb8504c1a in event_dispatch_epoll_handler (event=0x7f5ca8db1ec0, event_pool=0x7f5cba033c50) at event-epoll.c:572
#9  event_dispatch_epoll_worker (data=0x7f5cba0425b0) at event-epoll.c:674
#10 0x00007f5cb781fdf5 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f5cb71661ad in clone () from /lib64/libc.so.6
(gdb)
```

As we can observe, thread 6 is in the process of exiting the process. It has already run the exit handlers, which cleanup things that require cleaning up. This includes liburcu resources. By the time thread 1 calls rcu_bp_register(), the liburcu resources have been cleaned up. rcu_bp_register tries to access these non-existent resources, which leads to the segmentation fault.

Races like this are hard to fix. As this race and crash happen when the process is almost at the point of stopping, it doesn't have any serious impact to functionality apart from the core file and the log message. I'm setting a lower priority for this bug.

--- Additional comment from Kaushal on 2015-04-08 06:23:43 EDT ---

The fix should be simple enough. GlusterD's fini() doesn't stop tcp socket listener. If it did, the above situation wouldn't arise as the listener would have been stopped before the liburcu exit handler was called.

--- Additional comment from Anand Avati on 2015-04-10 07:42:37 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: This patch stops tcp/ip listeners during  glusterd exit.) posted (#1) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-04-13 05:03:52 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#2) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-04-16 05:18:47 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#3) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-04-24 07:14:46 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit.) posted (#4) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-12 05:31:12 EDT ---

REVIEW: http://review.gluster.org/10758 (ligglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#1) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-12 05:44:28 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#2) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-12 14:39:11 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#3) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-13 07:01:22 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#4) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-14 15:00:23 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#5) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-14 15:23:41 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#6) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-20 05:05:47 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#7) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-21 23:55:47 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#9) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-22 02:14:01 EDT ---

REVIEW: http://review.gluster.org/10758 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#10) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-22 09:49:15 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#6) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-22 10:24:10 EDT ---

REVIEW: http://review.gluster.org/10894 (bglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#2) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-22 12:46:01 EDT ---

REVIEW: http://review.gluster.org/10894 (bglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#3) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-23 07:10:11 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#7) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-23 07:17:57 EDT ---

REVIEW: http://review.gluster.org/10894 (bglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#4) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-23 07:18:00 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit.) posted (#8) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-23 07:42:48 EDT ---

REVIEW: http://review.gluster.org/10894 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#5) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-23 07:42:51 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#9) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-23 13:00:22 EDT ---

REVIEW: http://review.gluster.org/10894 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#6) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-24 05:39:58 EDT ---

REVIEW: http://review.gluster.org/10894 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#7) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-05-24 05:40:00 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#10) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Christopher Pereira on 2015-05-25 17:33:03 EDT ---



--- Additional comment from Anand Avati on 2015-05-28 00:46:50 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#11) for review on master by Atin Mukherjee (amukherj)

--- Additional comment from Anand Avati on 2015-05-28 01:21:30 EDT ---

REVIEW: http://review.gluster.org/10894 (glusterfsd: Enabling the fini()  in cleanup_and_exit()) posted (#8) for review on master by Kaushal M (kaushal)

--- Additional comment from Anand Avati on 2015-05-28 01:22:01 EDT ---

REVIEW: http://review.gluster.org/10894 (glusterfsd: Enabling the fini()  in cleanup_and_exit()) posted (#9) for review on master by Kaushal M (kaushal)

--- Additional comment from Anand Avati on 2015-05-28 21:13:38 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#12) for review on master by Krishnan Parthasarathi (kparthas)

--- Additional comment from Anand Avati on 2015-05-30 00:25:05 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#13) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-06-01 02:15:28 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#14) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-06-01 04:37:28 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#15) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-06-01 23:35:10 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#16) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-06-03 04:37:42 EDT ---

REVIEW: http://review.gluster.org/10894 (libglusterfs: Enabling the fini()  in cleanup_and_exit()) posted (#10) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-06-03 04:37:45 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#17) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-06-03 04:43:02 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#18) for review on master by Anand Nekkunti (anekkunt)

--- Additional comment from Anand Avati on 2015-06-03 04:56:27 EDT ---

REVIEW: http://review.gluster.org/10197 (glusterd: Stop tcp/ip listeners during  glusterd exit) posted (#19) for review on master by Anand Nekkunti (anekkunt)

Comment 1 Anand Avati 2015-06-16 10:34:01 UTC
COMMIT: http://review.gluster.org/11154 committed in release-3.7 by Atin Mukherjee (amukherj) 
------
commit c58a15811a82c675a4cc20d664731239daa0c48c
Author: anand <anekkunt>
Date:   Fri Apr 10 16:41:25 2015 +0530

    glusterd: Stop tcp/ip listeners during  glusterd exit
    
    Problem : Because of race between exit thread and rpc thread
    causing the glusterd crash while glusterd exiting/stoping.
    
    Fix : Stop tcp/ip socket listeners in cleanup_and_exit to
    avoid new rpc events.
    
    Backport of :
    >Change-Id: Ie9280c8c9d7c350a176529375d861432f3de94ac
    >BUG: 1209461
    >Signed-off-by: anand <anekkunt>
    >Reviewed-on: http://review.gluster.org/10197
    >Reviewed-by: Atin Mukherjee <amukherj>
    >Tested-by: NetBSD Build System <jenkins.org>
    >Reviewed-by: Kaushal M <kaushal>
    
    Change-Id: Ibb3d3669e248af8c5284801d7f18c6ee26fe2ef3
    BUG: 1230026
    Reviewed-on: http://review.gluster.org/11154
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 2 Anand Avati 2015-06-17 04:15:32 UTC
COMMIT: http://review.gluster.org/11155 committed in release-3.7 by Atin Mukherjee (amukherj) 
------
commit 6724ae3b3becdf6be495e8b4f81f1fba302da69e
Author: anand <anekkunt>
Date:   Fri May 22 18:18:11 2015 +0530

    libglusterfs: Enabling the fini()  in cleanup_and_exit()
    
    Problem 1 : glusterd was crashing due to race between clean up thread and rpc event thread.
    
    Scenario:
    As we can observed, X thread is in the process of exiting the process. It has already
    run the exit handlers, which cleanup things that require cleaning up. This includes
    liburcu resources. By the time Y thread  called rcu_bp_register(), the liburcu resources
    have been cleaned up. rcu_bp_register() tries to access these non-existent resources,
    which leads to the segmentation fault.
    
    Note1:
    Crash happen when the process is almost at the point of stopping(exiting), it doesn't have any
    serious impact to functionality apart from creating the core dump file and the log message.
    
    Fix .Do proper clean up before calling exit().
    
    Note2: Other xlator have clean up issues,so only glusterd clean up function invoked.
    
    Note3: This patch also solve the selinux issue.
    
    Problem 2 : glusterd runs as rpm_script_t when it's executed from the rpm scriptlet,files created
    in this context are set as rpm_script_t, so glusterd unable to access these files when it runs
    in glusterd_t context.
    
    Fix: Fini clean up the files while glusterd exiting, so files are recreated by glusterd while
    starting with proper SElinux context label.
    
    Backport of :
    >Change-Id: Idcfd087f51c18a729bdf44a146f9d294e2fca5e2
    >BUG: 1209461
    >Signed-off-by: anand <anekkunt>
    >Reviewed-on: http://review.gluster.org/10894
    >Tested-by: Gluster Build System <jenkins.com>
    >Reviewed-by: Atin Mukherjee <amukherj>
    >Tested-by: NetBSD Build System <jenkins.org>
    >Reviewed-by: Raghavendra Bhat <raghavendra>
    >Reviewed-by: Vijay Bellur <vbellur>
    
    Change-Id: I59579e675bd73d7a19f7b965bd2c3c0fcd95d241
    BUG: 1230026
    Signed-off-by: anand <anekkunt>
    Reviewed-on: http://review.gluster.org/11155
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 3 Niels de Vos 2015-06-20 09:50:28 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.2, please reopen this bug report.

glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist [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://www.gluster.org/pipermail/packaging/2015-June/000006.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user