Bug 1139170

Summary:	DHT :- rm -rf is not removing stale link file and because of that unable to create file having same name as stale link file
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.2	CC:	gluster-bugs, nsathyan, racpatel, spalai, ssamanta
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.5.3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1117923	Environment:
Last Closed:	2014-11-21 16:02:20 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:	1117283, 1117923, 1139992
Bug Blocks:	1125231, 1138389

Comment 1 Anand Avati 2014-09-15 07:27:40 UTC

REVIEW: http://review.gluster.org/8715 (DHT/Create : Failing to identify a linkto file in lookup_everywhere_cbk path) posted (#1) for review on release-3.5 by N Balachandran (nbalacha)

Comment 2 Anand Avati 2014-09-17 15:34:06 UTC

COMMIT: http://review.gluster.org/8715 committed in release-3.5 by Niels de Vos (ndevos) 
------
commit 3f886a345d4cb0d4760cadd0ab5fd94c0b7209a6
Author: Susant Palai <spalai>
Date:   Wed Sep 10 21:34:37 2014 +0530

    DHT/Create : Failing to identify a linkto file in lookup_everywhere_cbk path
    
    In case a file is not found in its cached subvol we proceed with
    dht_lookup_everywhere. But as we dont add the linkto xattr to the
    dictionary, we fail to identify any linkto file encountered.The
    implication being we end up thinking the linkto file as a regular file
    and proceed with the fop.
    
    Change-Id: Iab02dc60e84bb1aeab49182f680c0631c33947e2
    BUG: 1139170
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/8277
    Reviewed-by: Vijay Bellur <vbellur>
    Tested-by: Gluster Build System <jenkins.com>
    (cherry picked from commit 52da727e7564963a8a244fc5cb7028315e458529)
    Signed-off-by: Nithya Balachandran <nbalacha>
    Reviewed-on: http://review.gluster.org/8715
    Reviewed-by: Jeff Darcy <jdarcy>

Comment 3 Niels de Vos 2014-10-05 12:59:54 UTC

The first (and last?) Beta for GlusterFS 3.5.3 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.3beta1 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-October/018990.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-05 09:24:35 UTC

The second Beta for GlusterFS 3.5.3 has been released [1]. Please verify if the release solves this bug report for you. In case the glusterfs-3.5.3beta2 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 have been made available on [2] to make testing easier.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019359.html
[2] http://download.gluster.org/pub/gluster/glusterfs/qa-releases/3.5.3beta2/

Comment 5 Niels de Vos 2014-11-21 16:02:20 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.5.3, please reopen this bug report.

glusterfs-3.5.3 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://supercolony.gluster.org/pipermail/announce/2014-November/000042.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/