Bug 1222748 - server_readdirp_cbk links inodes that don't have the .glusterfs/gfid link
Summary: server_readdirp_cbk links inodes that don't have the .glusterfs/gfid link
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-19 04:24 UTC by Ravishankar N
Modified: 2018-08-29 03:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-29 03:53:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Ravishankar N 2015-05-19 04:24:35 UTC
Description of problem:
posix_lookup triggers a gfid heal only of loc->inode->gfid is not null. But if a readdirp comes on the parent dir before the lookup, the inode is linked and the gfid never heals. 

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


How reproducible:
Always

Steps to Reproduce:
1. Apply http://review.gluster.org/#/c/10667/ and run `tests/basic/afr/data-self-heal.t`. Tests will fail because heal was not successful due to absence of 
the gfid hardlink


Expected results:
server readdirp must only link inodes  that have a valid gfid link.

Comment 1 Amar Tumballi 2018-08-29 03:53:20 UTC
Lot of time since no activity on this bug. We have either fixed it already or it is mostly not critical anymore!

Please re-open the bug if the issue is burning for you, or you want to take the bug to closure with fixes.


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