Bug 1356497 - Provide script to create index files
Summary: Provide script to create index files
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
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: 2016-07-14 09:16 UTC by Anuradha
Modified: 2018-08-29 03:35 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.1.3 (or later)
Clone Of:
Environment:
Last Closed: 2018-08-29 03:35:23 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Anuradha 2016-07-14 09:16:25 UTC
Description of problem:
Recently a bug was raised where index files in indices/xattrop were not created after an upgrade from glusterfs-3.6.x to glusterfs-3.7.9 was done. In such cases where index files were not created due to some reason, there needs to be a way of identifying files that need heal and be added in heal queue.

Providing a script to do the same helps.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-07-14 11:01:52 UTC
REVIEW: http://review.gluster.org/14913 (extras: provide a script to generate index files) posted (#4) for review on master by Anuradha Talur (atalur)

Comment 2 Vijay Bellur 2016-07-15 09:36:17 UTC
REVIEW: http://review.gluster.org/14913 (extras: provide a script to generate index files) posted (#5) for review on master by Anuradha Talur (atalur)

Comment 3 Vijay Bellur 2016-07-19 10:00:05 UTC
REVIEW: http://review.gluster.org/14913 (extras: provide a script to generate index files) posted (#6) for review on master by Anuradha Talur (atalur)

Comment 6 Amar Tumballi 2018-08-29 03:35:23 UTC
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.


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