Bug 1295360

Summary:	[Tier]: can not delete symlinks from client using rm
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	tiering	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.7.7	CC:	bugs, dlambrig, nbalacha, nchilaka, rhinduja, rhs-bugs
Target Milestone:	---	Keywords:	Regression, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1293963	Environment:
Last Closed:	2016-04-19 07:23:50 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:	1293903, 1293963
Bug Blocks:	1293237, 1309567

Comment 1 Vijay Bellur 2016-01-04 09:20:16 UTC

REVIEW: http://review.gluster.org/13164 (tier/unlink: open fd for special file for fdstat) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Vijay Bellur 2016-02-10 05:49:37 UTC

REVIEW: http://review.gluster.org/13164 (tier/unlink: open fd for special file for fdstat) posted (#2) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 3 Vijay Bellur 2016-02-22 14:52:23 UTC

COMMIT: http://review.gluster.org/13164 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 28f561b1855d118202de3a6d454d688c1ccb9e6e
Author: Mohammed Rafi KC <rkavunga>
Date:   Mon Dec 21 14:18:26 2015 +0530

    tier/unlink: open fd for special file for fdstat
    
    DUring unlink of a file, dht request stat to see whether
    the file is under migration or not. But in posix_unlink
    currently we are opening for regular files. so the fdstat
    for special files are failing with EBAD
    
    backport of>
    >Change-Id: Ic0678e42e7701c3dffb91d98272e664b0fc646b5
    >BUG: 1293256
    >Signed-off-by: Mohammed Rafi KC <rkavunga>
    >Reviewed-on: http://review.gluster.org/13034
    >Reviewed-by: Raghavendra G <rgowdapp>
    >Reviewed-by: Susant Palai <spalai>
    >Tested-by: NetBSD Build System <jenkins.org>
    >Reviewed-by: Dan Lambright <dlambrig>
    >Tested-by: Dan Lambright <dlambrig>
    
    Change-Id: Ibad6e97cb052f779520968f0dce15b6fa78a5e1a
    BUG: 1295360
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/13164
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Dan Lambright <dlambrig>

Comment 4 Kaushal 2016-04-19 07:23:50 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