Please have a public bugzilla description captured.
Here's a summary of the bug description and analysis. Heketi sometimes fails to delete the underlying LVs that formed the bricks, when it deletes a volume. This happens because the multiplexed brick process, doesnot correctly stop the brick graph, and leaves open a few files on the brick filesystem. This prevents the brick filesystem from being unmounted, and the LV from being destroyed. The open files in question, as possibly of the CTR xlator.
COMMIT: https://review.gluster.org/19025 committed in master by \"MOHIT AGRAWAL\" <moagrawa> with a commit message- features/changelog: changelog threads are not cleaned properly after receive GF_EVENT_CLEANUP Problem: changelog threads are not cleaned properly after receive GF_EVENT_CLEANUP while brick mux is enabled Solution: change changelog notify code path to cleanup threads properly BUG: 1524816 Change-Id: I007f4e14e3d557707df738faf222b78c793d5ab5 Signed-off-by: Mohit Agrawal <moagrawa>
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-4.0.0, please open a new bug report. glusterfs-4.0.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://lists.gluster.org/pipermail/announce/2018-March/000092.html [2] https://www.gluster.org/pipermail/gluster-users/