Bug 1459530
Summary: | [RFE] Need a way to resolve gfid split brains | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Karthik U S <ksubrahm> |
Component: | replicate | Assignee: | Karthik U S <ksubrahm> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | mainline | CC: | amukherj, bugs, nchilaka, ravishankar, rhs-bugs, storage-qa-internal |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.12.0 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | 1413959 | Environment: | |
Last Closed: | 2017-08-23 10:08:43 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: | |||
Bug Blocks: | 1413959, 1531934 |
Comment 1
Worker Ant
2017-06-07 12:05:58 UTC
REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#2) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#3) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#4) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#5) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#6) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#7) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#8) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#9) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#10) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#11) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#12) for review on master by Karthik U S (ksubrahm) REVIEW: https://review.gluster.org/17485 (cluster/afr: GFID split-brain resolution with existing CLI) posted (#13) for review on master by Karthik U S (ksubrahm) COMMIT: https://review.gluster.org/17485 committed in master by Jeff Darcy (jeff.us) ------ commit 657d78dbad118e511e1fca8b1badb9f8ae7a6f60 Author: karthik-us <ksubrahm> Date: Wed Jun 7 15:56:13 2017 +0530 cluster/afr: GFID split-brain resolution with existing CLI Problem: Currently there is no way for the admin from CLI to resolve gfid split-brain based on some policy like choice of the brick, mtime or size. Fix: With the existing CLI options based on size, mtime, and choice of brick, we do lookup on the parent for the specified file. As part of the lookup, if we find gfid mismatch, we resolve them based on the policy and return. If the file is not in gfid split- brain, then we check for the data and metadata split-brain in the getxattr code path, and resolve if any. This will work provided absolute path to the file with the CLI and not with gfid of the file. Hence the source-brick policy without any file path will also not resolve the gfid split-brain since it uses the gfid of the files. But it can resolve any other type of split-brains and skip the gfid mismatch resolution with the usual error message. Reverting the change https://review.gluster.org/17290. This patch resolves the issue. Fixes gluster/glusterfs#135 Change-Id: Iaeba6fc32f184a34255d03be87cda02773130a09 BUG: 1459530 Signed-off-by: karthik-us <ksubrahm> Reviewed-on: https://review.gluster.org/17485 Reviewed-by: Ravishankar N <ravishankar> Reviewed-by: Pranith Kumar Karampuri <pkarampu> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> 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.12.0, please open a new bug report. glusterfs-3.12.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://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/ |