Bug 1461717 - Not release the .glusterfs directory after volume stop when cluster.brick-multiplex=on
Summary: Not release the .glusterfs directory after volume stop when cluster.brick-mul...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 3.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-15 09:24 UTC by jsvisa
Modified: 2018-06-20 18:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description jsvisa 2017-06-15 09:24:49 UTC
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:

Comment 1 Shyamsundar 2018-06-20 18:28:06 UTC
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.

Comment 2 Shyamsundar 2018-06-20 18:28:09 UTC
This bug reported is against a version of Gluster that is no longer maintained
(or has been EOL'd). See https://www.gluster.org/release-schedule/ for the
versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline
gluster repository, request that it be reopened and the Version field be marked
appropriately.


Note You need to log in before you can comment on or make changes to this bug.