Bug 1443027 - Accessing file from aux mount is not triggering afr selfheals.
Summary: Accessing file from aux mount is not triggering afr selfheals.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-18 10:53 UTC by Ravishankar N
Modified: 2019-08-05 08:30 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-05 08:30:06 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Ravishankar N 2017-04-18 10:53:56 UTC
Description of problem:
Found while debugging a workaround that we wanted to suggest to a customer to speed up pending self-heals.

How reproducible:
Always.

Steps to Reproduce:
1.Get the list of gfids that need heal from .glusterfs/indices/xattrop

2.Do an aux mount of the volume:
glusterfs --aux-gfid-mount --volfile-id=<volanme> --volfile-server=server-I.P. /path/to/mount 

3. For each gfid, do a dummy getfattr:
getfattr -n user.no_such_attr /path/to/mount/.gfid/gfid-string

Actual results:
Background self-heal is not triggered from the mount.

Expected results:
The getxattr should trigger a background heal.

Comment 1 Worker Ant 2017-04-18 10:57:28 UTC
REVIEW: https://review.gluster.org/17072 (afr: reset inode event_gen in afr_discover_done) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Amar Tumballi 2019-05-11 10:43:41 UTC
As the patch is now abandoned.

Comment 3 Ravishankar N 2019-08-05 08:30:06 UTC
I'm not planning to work on this bug any time soon. In the interest of reducing bug backlog count, I am closing it. Please feel free to re-open as needed.


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