Bug 1339071 - dht/rebalance: mark hardlink migration failure as skipped for rebalance process
Summary: dht/rebalance: mark hardlink migration failure as skipped for rebalance process
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-24 05:59 UTC by Susant Kumar Palai
Modified: 2017-03-27 18:12 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.9.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-27 18:12:32 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Susant Kumar Palai 2016-05-24 05:59:37 UTC
Description of problem:
Hard link migration is not currently supported for rebalance(not remove-brick) process. Hence, mark them as skipped rather than failed as it creates confusion to users.

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-05-24 06:13:19 UTC
REVIEW: http://review.gluster.org/14493 (dht/rebalance: mark hardlink failures as skipped in rebalance) posted (#2) for review on master by Susant Palai (spalai)

Comment 2 Vijay Bellur 2016-05-25 14:19:30 UTC
COMMIT: http://review.gluster.org/14493 committed in master by Jeff Darcy (jdarcy) 
------
commit 1a489f8f67a98644e6ebea652dcf96dd7425046e
Author: Susant Palai <spalai>
Date:   Mon May 23 12:09:10 2016 +0530

    dht/rebalance: mark hardlink failures as skipped in rebalance
    
    Since rebalance(not remove-brick) process does not migrate hardlinks
    mark them as skipped rather than failed as it creates confusion for
    the users.
    
    Change-Id: I5d469d10146274f00bb91482d0373c5235a9b8b2
    BUG: 1339071
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/14493
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Smoke: Gluster Build System <jenkins.com>
    Reviewed-by: N Balachandran <nbalacha>

Comment 3 Shyamsundar 2017-03-27 18:12:32 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report.

glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/


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