Bug 1290965
Summary: | [Tiering] + [DHT] - Detach tier fails to migrate the files when there are corrupted objects in hot tier. | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Ravishankar N <ravishankar> | |
Component: | replicate | Assignee: | Ravishankar N <ravishankar> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | asrivast, bugs, dlambrig, josferna, knarra, nbalacha, nchilaka, sankarshan | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1289228 | |||
: | 1293300 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:50:01 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: | 1289228 | |||
Bug Blocks: | 1293300 |
Description
Ravishankar N
2015-12-12 06:36:12 UTC
REVIEW: http://review.gluster.org/12955 (afr: handle bad objects during lookup) posted (#1) for review on master by Ravishankar N (ravishankar) REVIEW: http://review.gluster.org/12955 (afr: handle bad objects during lookup) posted (#2) for review on master by Ravishankar N (ravishankar) REVIEW: http://review.gluster.org/12955 (afr: handle bad objects during lookup/inode_refresh) posted (#3) for review on master by Ravishankar N (ravishankar) REVIEW: http://review.gluster.org/12955 (afr: handle bad objects during lookup/inode_refresh) posted (#4) for review on master by Ravishankar N (ravishankar) REVIEW: http://review.gluster.org/12955 (afr: handle bad objects during lookup/inode_refresh) posted (#5) for review on master by Ravishankar N (ravishankar) REVIEW: http://review.gluster.org/12955 (afr: handle bad objects during lookup/inode_refresh) posted (#6) for review on master by Ravishankar N (ravishankar) REVIEW: http://review.gluster.org/12955 (afr: handle bad objects during lookup/inode_refresh) posted (#7) for review on master by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/12955 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 2b7226f9d3470d8fe4c98c1fddb06e7f641e364d Author: Ravishankar N <ravishankar> Date: Sat Dec 12 11:49:20 2015 +0530 afr: handle bad objects during lookup/inode_refresh If an object (file) is marked bad by bitrot, do not consider the brick on which the object is present as a potential read subvolume for AFR irrespective of the pending xattr values. Also do not consider the brick containing the bad object while performing afr_accuse_smallfiles(). Otherwise if the bad object's size is bigger, we may end up considering that as the source. Change-Id: I4abc68e51e5c43c5adfa56e1c00b46db22c88cf7 BUG: 1290965 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/12955 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> REVIEW: http://review.gluster.org/13044 (tests: handle bad objects during lookup/inode_refresh) posted (#2) for review on master by Ravishankar N (ravishankar) COMMIT: http://review.gluster.org/13044 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit a370013898585a87657ae41e4f266da5d98cc5d2 Author: Ravishankar N <ravishankar> Date: Mon Dec 21 12:07:51 2015 +0530 tests: handle bad objects during lookup/inode_refresh Change-Id: I1848f0e9243c9376e0deba6738757350fe8b704a BUG: 1290965 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/13044 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar> Reviewed-by: Pranith Kumar Karampuri <pkarampu> 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.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |