[Bugs] [Bug 1461717] New: Not release the .glusterfs directory after volume stop when cluster.brick-multiplex =on

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1461717

            Bug ID: 1461717
           Summary: Not release the .glusterfs directory after volume stop
                    when cluster.brick-multiplex=on
           Product: GlusterFS
           Version: 3.10
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: delweng at gmail.com
                CC: bugs at gluster.org



Description of problem:

I'm using the brick multiplex feature, which was added in version 3.10.
After created and started 3 volume, I'm going to destory one of the volumes.

After the volume is stop and deleted, I want to unmount the disk which is hold
by the volume before, but the unmount failed to a busy device.

Then using `lsof` to find who are using the files behind the disk, showed the
process glusterfsd are hold the files:

# lsof | grep /path/to/disk | awk '{print $10}' | sort -u
.glusterfs/brick.db
.glusterfs/brick.db-shm
.glusterfs/brick.db-wal


Version-Release number of selected component (if applicable):
3.10.3

How reproducible:


Steps to Reproduce:
1. gluster volume create a,b,c 
2. gluster volume start a,b,c
3. gluster volume stop b
4. gluster volume delete b
5. unmount the disk path to volume-b

Actual results:

unmount failed


Expected results:

unmount success


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.