Bug 1281265

Summary:	DHT :- log is full of ' Found anomalies in /<DIR> (gfid = 00000000-0000-0000-0000-000000000000)' - for each Directory which was self healed
Product:	[Community] GlusterFS	Reporter:	Sakshi <sabansal>
Component:	distribute	Assignee:	Sakshi <sabansal>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, mzywusko, nbalacha, neteler, racpatel, smohan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1114045
Clones:	1308410 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:44:23 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:	1114045
Bug Blocks:	1308410

Description Sakshi 2015-11-12 08:10:23 UTC

+++ This bug was initially created as a clone of Bug #1114045 +++

Description of problem:
=======================
cause of any reasons if Directory has been self healed, log has below messages where 0 GFIDs are dumped in the log rather than the actual GFID of the directory.

:[2014-06-25 08:52:50.339861] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /zile (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0




Version-Release number of selected component (if applicable):
=============================================================
3.6.0.19-1.el6rhs.x86_64

How reproducible:
=================
always

Steps to Reproduce:
===================
1.Create and mount Distributed Volume
2. Create Directories from mount point and make sure It is not created on all up sub-volumes.
3. send lookup from another mount point.
4. check logs for self-healed Directory 0 GFIDs are dumped rather than actual

Actual results:
===============
[2014-06-25 08:52:50.339861] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /zile (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0

Expected results:
=================
should show Actual GFID of Directory


Additional info:
================


[root@OVM3 nfs]# gluster v status snap
Status of volume: snap
Gluster process						Port	Online	Pid
------------------------------------------------------------------------------
Brick 10.70.35.198:/brick2/b1				49157	Y	13611
Brick 10.70.35.198:/brick2/b2				49158	Y	13345
Brick 10.70.35.198:/brick2/b3				49159	Y	13356
NFS Server on localhost					2049	Y	13623
NFS Server on 10.70.35.240				2049	Y	19185
NFS Server on 10.70.35.172				2049	Y	13465
 
Task Status of Volume snap
------------------------------------------------------------------------------
There are no active volume tasks

log snippet:-
[2014-06-27 07:53:07.260193] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /dir2 (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0
[2014-06-27 07:56:39.896560] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /dir2 (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0
[2014-06-27 08:02:41.481429] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /dir2 (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0
[2014-06-27 08:04:39.932597] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /dir2 (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0
[2014-06-27 08:06:52.812528] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /dir2 (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0
[2014-06-27 08:08:59.461588] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /abc (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0
[2014-06-27 10:21:46.216573] I [dht-layout.c:663:dht_layout_normalize] 0-snap-dht: Found anomalies in /abc (gfid = 00000000-0000-0000-0000-000000000000). Holes=1 overlaps=0

Comment 1 Vijay Bellur 2015-11-12 08:14:55 UTC

REVIEW: http://review.gluster.org/12574 (dht: loc should store proper gfid) posted (#1) for review on master by Sakshi Bansal

Comment 2 Vijay Bellur 2015-11-17 09:46:44 UTC

COMMIT: http://review.gluster.org/12574 committed in master by Raghavendra G (rgowdapp) 
------
commit b6323c1995223d3566ffca12145c943df3fdc2ed
Author: Sakshi Bansal <sabansal>
Date:   Thu Nov 12 13:43:31 2015 +0530

    dht: loc should store proper gfid
    
    Change-Id: Ic1393d44a9ed4aaba23d7c9ddea45977b9dae5e4
    BUG: 1281265
    Signed-off-by: Sakshi Bansal <sabansal>
    Reviewed-on: http://review.gluster.org/12574
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 3 Niels de Vos 2016-06-16 13:44:23 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.8.0, please open a new bug report.

glusterfs-3.8.0 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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user