Bug 1774598
Summary: | GlusterFS gets corrupted when moves are done when capacity is 100% | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Rob de Wit <rob.dewit> |
Component: | core | Assignee: | bugs <bugs> |
Status: | CLOSED UPSTREAM | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6 | CC: | bugs, moagrawa, pasik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-03-12 12:17:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rob de Wit
2019-11-20 14:26:01 UTC
I believe the issue should be fixed after backporting the patch(https://review.gluster.org/#/c/glusterfs/+/23572/) in release 6.0. Would it be possible for you to try to reproduce the issue after apply the same patch? Thanks, Mohit Agrawal @Mohit I need some time to test this properly - will come back and report. The original setup is no longer available for testing this. When I try to reproduce it on (slower) hardware I cannot reproduce the error, so I can't tell if the patch fixes the problem :-( This bug is moved to https://github.com/gluster/glusterfs/issues/862, and will be tracked there from now on. Visit GitHub issues URL for further details |