Bug 1306163

Summary:	[USS]: If .snaps already exists, ls -la lists it even after enabling USS
Product:	[Community] GlusterFS	Reporter:	Vijaikumar Mallikarjuna <vmallika>
Component:	snapshot	Assignee:	Vijaikumar Mallikarjuna <vmallika>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.7	CC:	asengupt, asriram, bugs, rhinduja, rjoseph, smohan, storage-qa-internal, vmallika
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	USS
Fixed In Version:	glusterfs-3.7.9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1303828	Environment:
Last Closed:	2016-04-19 07:25:16 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:	1159283, 1170502, 1303593, 1303595, 1303828
Bug Blocks:	1153907

Comment 1 Vijay Bellur 2016-02-10 08:24:34 UTC

REVIEW: http://review.gluster.org/13419 (USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled) posted (#1) for review on release-3.7 by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Vijay Bellur 2016-02-12 06:28:34 UTC

REVIEW: http://review.gluster.org/13419 (USS: pre-existing .snaps should not be listed with 'ls -a' with USS enabled) posted (#2) for review on release-3.7 by Vijaikumar Mallikarjuna (vmallika)

Comment 3 Vijay Bellur 2016-02-15 08:27:17 UTC

COMMIT: http://review.gluster.org/13419 committed in release-3.7 by Rajesh Joseph (rjoseph) 
------
commit b47f741b5f42d2e7d994cd06e1c1c679fd9e9535
Author: vmallika <vmallika>
Date:   Wed Feb 10 13:53:12 2016 +0530

    USS: pre-existing .snaps should not be listed with 'ls -a' with USS
    enabled
    
    This is a backport of http://review.gluster.org/#/c/13330/
    
    If there is a .snaps directory pre-exists and when USS is enabled,
    it should not be listed with 'ls -a'
    
    > Change-Id: I1c43e2decc0bbbd3213b190b675e3a32d04b22d3
    > BUG: 1303828
    > Signed-off-by: vmallika <vmallika>
    
    Change-Id: I76c632239b45f7eb7296cbfe3b73bc68e5bd1655
    BUG: 1306163
    Signed-off-by: vmallika <vmallika>
    Reviewed-on: http://review.gluster.org/13419
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>

Comment 4 Kaushal 2016-04-19 07:25:16 UTC

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.7.9, please open a new bug report.

glusterfs-3.7.9 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] https://www.gluster.org/pipermail/gluster-users/2016-March/025922.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user