Bug 1787014 - Partial rename leads to both the source and destination files to be available after the heal
Summary: Partial rename leads to both the source and destination files to be available...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Sheetal Pamecha
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-30 11:15 UTC by Sheetal Pamecha
Modified: 2020-03-12 14:25 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 14:25:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Sheetal Pamecha 2019-12-30 11:15:27 UTC 
Description of problem:
In EC volume with n=k+m configuration if any number of bricks less than or equal to m are down and a rename is performed it will lead to both the source and destination files to be available after the heal.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Sheetal Pamecha 2020-02-05 06:01:39 UTC 
Solution:
The solution is proposed here -
https://docs.google.com/document/d/1xJs1pvujxt6-wHJ-l3r5WXQxlXVBh5BVZarwh2F7CCg/edit
Comment 2 Sheetal Pamecha 2020-02-19 05:05:55 UTC 
Upstream patch - https://review.gluster.org/#/c/glusterfs/+/23937/
Comment 3 Worker Ant 2020-03-12 14:25:39 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/1048, 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.