Bug 1408414 - Remove-brick rebalance failed while rm -rf is in progress
Summary: Remove-brick rebalance failed while rm -rf is in progress
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: 3.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL:
Whiteboard:
Depends On: 1405000 1408115 1410355 1410764
Blocks: 1408138
TreeView+ depends on / blocked
 
Reported: 2016-12-23 10:24 UTC by Susant Kumar Palai
Modified: 2017-01-16 12:27 UTC (History)
9 users (show)

Fixed In Version: glusterfs-3.8.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1408115
Environment:
Last Closed: 2017-01-16 12:27:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Worker Ant 2016-12-23 10:44:43 UTC 
REVIEW: http://review.gluster.org/16278 (dht/rebalance: reverify lookup failures) posted (#1) for review on release-3.8 by Susant Palai (spalai)
Comment 2 Worker Ant 2016-12-28 05:54:44 UTC 
COMMIT: http://review.gluster.org/16278 committed in release-3.8 by Raghavendra G (rgowdapp) 
------
commit 58deefde3c279fd867304118d60970bdfa72cd93
Author: Susant Palai <spalai>
Date:   Tue Dec 13 14:26:53 2016 +0530

    dht/rebalance: reverify lookup failures
    
    race: readdirp has read one entry, and doing a lookup on
    that entry, but user might have renamed/removed that entry just
    after readdirp but before lookup.
    
    Since remove-brick is a costly opertaion,will ingore any
    ENOENT/ESTALE failures and move on.
    
    > Change-Id: I62c7fa93c0b9b7e764065ad1574b97acf51b5996
    > BUG: 1408115
    > Signed-off-by: Susant Palai <spalai>
    > Reviewed-on: http://review.gluster.org/15846
    > Reviewed-by: Raghavendra G <rgowdapp>
    > Smoke: Gluster Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    
    Change-Id: I62c7fa93c0b9b7e764065ad1574b97acf51b5996
    BUG: 1408414
    Reviewed-on: http://review.gluster.org/15846
    Reviewed-by: Raghavendra G <rgowdapp>
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    (cherry picked from commit c20febcb1ffaef3fa29563987e7a3b554aea27b3)
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/16278
Comment 3 Niels de Vos 2017-01-16 12:27:41 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.8.8, please open a new bug report.

glusterfs-3.8.8 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] https://lists.gluster.org/pipermail/announce/2017-January/000064.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.