Bug 1266841
Summary: | Data Tiering:Data Loss:File migrations(flushing of data) to cold tier fails on detach tier with quota limits reached | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Nag Pavan Chilakam <nchilaka> | |
Component: | tiering | Assignee: | Raghavendra G <rgowdapp> | |
Status: | CLOSED EOL | QA Contact: | bugs <bugs> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 3.7.4 | CC: | bugs, nchilaka, sankarshan | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1278419 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-08 11:03:12 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: | ||||
Bug Depends On: | 1265623, 1267812 | |||
Bug Blocks: | 1260923, 1278419 |
Description
Nag Pavan Chilakam
2015-09-28 07:30:29 UTC
sosreports.eng.blr.redhat.com:/home/repo/sosreports/bug.1266841 Hi Nag Pavan, What is the re-balance status? does it show any failure numbers. In this case it is expected that files that have failed to migrate will can be lost when commit is performed Yes, there are failures under rebalance. But given that detach tier must just move files b/w bricks and the end user doesn't bother about how it is done. We must not be seeing any failures. May be I should change the title. In Short "quotas must not stop data being moved from hot to cold tier during a detach tier" Patch submitted: http://review.gluster.org/#/c/12266/ This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release. |