andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

posix: brick process crash after stop the volume while brick mux is on

Browse Source 
Problem: sometime brick process is getting crash after stop the volume
         while brick mux is enabled and no. of volumes are high

Solution: In posix notify at the time close mount_lock dir , dir handle
          needs to set NULL to avoid the reuse of same dir handle.

BUG: 1470533
Change-Id: Ifd41c20b3c597317851f91049a7c801949840b16
Signed-off-by: Mohit Agrawal <moagrawa@redhat.com>
Reviewed-on: https://review.gluster.org/17767
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Amar Tumballi <amarts@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
This commit is contained in:
Mohit Agrawal 2017-07-13 12:23:13 +05:30 committed by Jeff Darcy
parent f367671d45
commit 61db7125a5
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xlators/storage/posix/src/posix.c
View File

@ -6851,8 +6851,10 @@ notify (xlator_t *this,
(void) gf_thread_cleanup_xint (priv->fsyncer);
priv->fsyncer = 0;
}
if (priv->mount_lock)
if (priv->mount_lock) {
(void) sys_closedir (priv->mount_lock);
priv->mount_lock = NULL;
}
break;
default: