diff options
| author | Ravishankar N <ravishankar@redhat.com> | 2017-09-27 10:32:36 +0530 |
|---|---|---|
| committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2017-10-02 12:34:23 +0000 |
| commit | f5998f07dfd21d06a4119416ca79db50232b50d4 (patch) | |
| tree | b72521e7fd07cb7cec55029ad7bfbae9a12c62f2 /xlators/mount/fuse/src/fuse-bridge.c | |
| parent | 5eab919dee035b9cf1b7f060bcf2d9eaa1e92eb3 (diff) | |
afr: auto-resolve split-brains for zero-byte files
Backport of https://review.gluster.org/#/c/18283/
Problems:
As described in BZ 1491670, renaming hardlinks can result in data/mdata
split-brain of the DHT link-to files (T files) without any mismatch of
data and metadata.
As described in BZ 1486063, for a zero-byte file with only dirty bits
set, arbiter brick will likely be chosen as the source brick.
Fix:
For zero byte files in split-brain, pick first brick as
a) data source if file size is zero on all bricks.
b) metadata source if metadata is the same on all bricks
In arbiter case, if file size is zero on all bricks and there are no
pending afr xattrs, pick 1st brick as data source.
Change-Id: I0270a9a2f97c3b21087e280bb890159b43975e04
BUG: 1496321
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
Reported-by: Rahul Hinduja <rhinduja@redhat.com>
Reported-by: Mabi <mabi@protonmail.ch>
Diffstat (limited to 'xlators/mount/fuse/src/fuse-bridge.c')
0 files changed, 0 insertions, 0 deletions