Bug 1362129
Summary: | rename of a file can cause data loss in an replica/arbiter volume configuration | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ravishankar N <ravishankar> |
Component: | replicate | Assignee: | Ravishankar N <ravishankar> |
Status: | CLOSED ERRATA | QA Contact: | Anees Patel <anepatel> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | rhgs-3.1 | CC: | amukherj, anepatel, asriram, bugs, nchilaka, pkarampu, ravishankar, rcyriac, rhinduja, rhs-bugs, sheggodu, srmukher, storage-qa-internal |
Target Milestone: | --- | Keywords: | Triaged, ZStream |
Target Release: | RHGS 3.4.z Batch Update 3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.12.2-33 | Doc Type: | Bug Fix |
Doc Text: |
In replica 3 volume, renaming a file while the brick with the 'good copy' of the file is down would result in removal of the file during self-heal, leading to data loss. With this release, lookup of a file will fail if there is no
good copy (as determined by AFR xattrs) found, dismissing the rename option and limiting the data loss.
|
Story Points: | --- |
Clone Of: | 1357000 | Environment: | |
Last Closed: | 2019-02-04 07:41:25 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: | 1357000, 1366818 | ||
Bug Blocks: | 1645480 |
Description
Ravishankar N
2016-08-01 10:47:59 UTC
http://review.gluster.org/15226 posted upstream for review. Verified the fix per the above test-plan for arbiter and replica 3, on the latest BU3 build # rpm -qa | grep gluster gluster-nagios-common-0.2.4-1.el7rhgs.noarch glusterfs-api-3.12.2-36.el7rhgs.x86_64 glusterfs-server-3.12.2-36.el7rhgs.x86_64 glusterfs-geo-replication-3.12.2-36.el7rhgs.x86_64 glusterfs-client-xlators-3.12.2-36.el7rhgs.x86_64 -Setting this to verified The doc text has been updated. Kindly review the technical accuracy. Made a minor change. Looks good to me otherwise. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0263 |