+++ This bug was initially created as a clone of Bug #1111612 +++ Description of problem: After snapshot many /tmp/xfsmountXXXX folders are created and they are never deleted. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: After snapshot many /tmp/xfsmountXXXX folders are created and they are never deleted. Expected results: No temporary folders should be seen after snapshot creation. Additional info:
REVIEW: http://review.gluster.org/8138 (glusterd/snapshot: delete temporary folder after snapshot create) posted (#1) for review on master by Rajesh Joseph (rjoseph)
REVIEW: http://review.gluster.org/8138 (glusterd/snapshot: delete temporary folder after snapshot create) posted (#2) for review on master by Rajesh Joseph (rjoseph)
COMMIT: http://review.gluster.org/8138 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 6ddb67c8f53bdfc5fb0ca2427b6f1a0112c49ecc Author: Rajesh Joseph <rjoseph> Date: Fri Jun 20 20:01:59 2014 +0530 glusterd/snapshot: delete temporary folder after snapshot create snapshot create create temporary folders in /tmp location with the name xfsmountXXXXXX. It should be cleaned up after snapshot create Change-Id: Idd0c480c1eee7f0fdeba92ae427510faac0f5234 BUG: 1111614 Signed-off-by: Rajesh Joseph <rjoseph> Reviewed-on: http://review.gluster.org/8138 Reviewed-by: Niels de Vos <ndevos> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users