Bug 1251614 - gf_defrag_fix_layout recursively fails, distracting from the root cause
Summary: gf_defrag_fix_layout recursively fails, distracting from the root cause
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Barak Sason Rofman
QA Contact:
Whiteboard: dht-failed-rebalance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-08-07 22:04 UTC by Joe Julian
Modified: 2020-03-12 14:49 UTC (History)
3 users (show)

Fixed In Version: glusterfs-6.x
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2020-03-12 14:49:36 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 24210 0 None Open dht/rebalance - fixing recursive failure issue 2020-03-10 09:25:47 UTC

Description Joe Julian 2015-08-07 22:04:17 UTC
In df_defrag_fix_layout if a recursive call to itself fails, all parent directories also fail (lines 2550-2560). I don't believe that the fix_layout actually fails on those parent directories as the extended attribute was applied  successfully in line 2539.

Comment 1 Amar Tumballi 2019-05-07 21:14:12 UTC
With introduction of commit-hash and other things in rebalance, this looks more fool proof, and didn't see any issues in latest codebase. Will mark it as WORKSFORME (with glusterfs-6.x) release. If the issue persists, will take it up in one of the future releases.

Comment 2 Nithya Balachandran 2019-05-08 03:28:18 UTC
Reopening this as this still exists.

Comment 4 Susant Kumar Palai 2020-02-18 08:23:07 UTC
I guess we can fix the issue by changing the state to STOP after encountering a fix-layout failure so that the callers won't report a failure.

Comment 5 Worker Ant 2020-03-10 09:25:50 UTC
REVIEW: https://review.gluster.org/24210 (dht/rebalance - fixing recursive failure issue) posted (#1) for review on master by Barak Sason Rofman

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

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