Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1696075

Summary: Client lookup is unable to heal missing directory GFID entry
Product: [Community] GlusterFS Reporter: Anees Patel <anepatel>
Component: replicateAssignee: Ravishankar N <ravishankar>
Status: CLOSED UPSTREAM QA Contact: Rahul Hinduja <rhinduja>
Severity: high Docs Contact:
Priority: high    
Version: 6CC: bugs, kiyer, ksubrahm, ravishankar
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-12 12:38:09 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:
Attachments:
Description Flags
glustomain_3_4_4.log none

Description Anees Patel 2019-04-04 06:44:07 UTC
Description of problem:

When dir gfid entry is missing on few backend bricks for a directory, client heal is unable to re-create the gfid entries after doing stat from client.
The automated test-case passes on downstream 3.4.4 but is failing on upstream gluster 6.

Version-Release number of selected component (if applicable):
Latest gluster 6

How reproducible:
Always,

Steps to Reproduce:
1. Create a 2X3 dist-replicated volume, and fuse mount it
2. Create a empty directory from mount point
3. Verify the gfid entry is present on all backend bricks for this dir
4. Delete gfid entry for 5 out of 6 backend bricks, brick{1..6}
5. Now trigger heal from mount pt.
#ls -l
#find . | xargs stat

6. Check backend bricks, the gfid entry should be healed for all the bricks.

Actual results:

At step 6, gfid entry is not created after client lookup.



Expected results:

Client lookup should trigger heal and gfid should be healed
Additional info:

There is also a latest fix per BZ#1661258, in which the dht delegates task to AFR when there is a missing gfid for all bricks in subvol, as per my understanding.

The test-case is automated and can be found at  https://review.gluster.org/c/glusto-tests/+/22480/
The test passes Downstream but fails upstream, the glusto logs for the failure can be found at https://ci.centos.org/job/gluster_glusto-patch-check/1277/artifact/glustomain.log

Comment 2 Anees Patel 2019-04-08 09:25:20 UTC
Created attachment 1553510 [details]
glustomain_3_4_4.log

Comment 4 Amar Tumballi 2019-05-27 15:36:59 UTC
Marking it back to NEW, as the assignee is still bugs

Comment 7 Worker Ant 2020-03-12 12:38:09 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/916, and will be tracked there from now on. Visit GitHub issues URL for further details