Bug 1492782 – self-heal daemon stuck

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1492782 - self-heal daemon stuck

Summary:	self-heal daemon stuck

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	replicate (Show other bugs)
Sub Component:
Version:	3.1
Hardware:	Unspecified Unspecified

Priority	high Severity unspecified
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	Ravishankar N
QA Contact:	Vijay Avuthu
Docs Contact:

URL:
Whiteboard:	rebase
Keywords:

Depends On:	1493415 1499202
Blocks:	1503135
	Show dependency tree / graph

Reported:	2017-09-18 11:41 EDT by Raghavendra Bhat
Modified:	2018-09-10 06:19 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	glusterfs-3.12.2-1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-09-04 02:36:24 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:2607	None	None	None	2018-09-04 02:38 EDT

Groups: None (edit)

Comment 12 Vijay Avuthu 2018-07-26 04:40:31 EDT

Update:
=========

Build Used: glusterfs-3.12.2-14.el7rhgs.x86_64

Verified below scenarios.

Scenario 1:

1) Create 1 * 3 volume and start
2) Disable self-heal-daemon 
3) Create file with data named f1 and empty file named f2
4) get the gfid of f2 from any of the bricks
5) remove gfid and .glusterfs hardlink from brick0 for f2 
6) Do name lookup from client 
7) gfid and .glusterfs hardlink should be created successfully

> Before name look

# getfattr -d -m . -e hex /bricks/brick1/b0/f2
getfattr: Removing leading '/' from absolute path names
# file: bricks/brick1/b0/f2
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.gfid2path.0e7737705d2193e8=0x30303030303030302d303030302d303030302d303030302d3030303030303030303030312f6632
#

> After name lookup

# getfattr -d -m . -e hex /bricks/brick1/b0/f2
getfattr: Removing leading '/' from absolute path names
# file: bricks/brick1/b0/f2
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.gfid=0x73ddf5fd1d89431c9ccc03a927c1c85c
trusted.gfid2path.0e7737705d2193e8=0x30303030303030302d303030302d303030302d303030302d3030303030303030303030312f6632
#

Scenario 2:

1) Create 1 * 3 volume and start
2) Disable self-heal-daemon 
3) create dir and touch file inside dir ( /dir/f1 )
4) get the gfid of f1 from any of the bricks
5) remove gfid and .glusterfs hardlink from brick0 for file f1
6) set the pending entry xattr on parent dir on brick1 and brick2
7) add gfid entry as hardlink to the base entry on brick1 and brick2 
8) enable self-heal-daemon
9) trigger volume heal and wait for heal to complete
10) gfid and .glusterfs hardlink should be created successfully


Changing status to Verified

Comment 14 errata-xmlrpc 2018-09-04 02:36:24 EDT

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.

https://access.redhat.com/errata/RHSA-2018:2607

Note You need to log in before you can comment on or make changes to this bug.