Bug 1111612

Summary:	[SNAPSHOT]: Temporary folders are created after snapshot create
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	rjoseph
Component:	snapshot	Assignee:	rjoseph
Status:	CLOSED ERRATA	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.0	CC:	nsathyan, rhs-bugs, ssamanta, storage-qa-internal, vagarwal
Target Milestone:	---
Target Release:	RHGS 3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	SNAPSHOT
Fixed In Version:	glusterfs-3.6.0.23-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1111614 (view as bug list)		Environment:
Last Closed:	2014-09-22 19:42:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1111614

Description rjoseph 2014-06-20 14:07:56 UTC

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:

Comment 3 rjoseph 2014-06-23 13:10:46 UTC

Patch sent to downstream: https://code.engineering.redhat.com/gerrit/#/c/27548/

Comment 4 Rahul Hinduja 2014-07-07 11:59:10 UTC

Verified with build: glusterfs-3.6.0.24-1.el6rhs.x86_64

No /tmp/xfsmountXXXX entry found after the snapshot is created.

[root@rhs-arch-srv2 tmp]# gluster snapshot list | wc
     99      99     690
[root@rhs-arch-srv2 tmp]# pwd
/tmp
[root@rhs-arch-srv2 tmp]# ls 
ks-script-YXIvnd  tmp.fgzGfI  yum.log
[root@rhs-arch-srv2 tmp]# 

Moving the bug to verified state.

Comment 6 errata-xmlrpc 2014-09-22 19:42:42 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1278.html