diff options
author | Ravishankar N <ravishankar@redhat.com> | 2018-05-18 15:38:29 +0530 |
---|---|---|
committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2018-05-25 12:57:45 +0000 |
commit | c6f21697a52200bbbf9af05dff2b9c3ae0a99b43 (patch) | |
tree | 1da294370544647de8e53a6ab0b2264aaf93f855 /xlators/cluster/afr/src/afr-dir-write.h | |
parent | dbe0984d8a84e0ca0e0d42f84d856c6f1d2a5134 (diff) |
afr: fix bug-1363721.t failure
Problem:
In the .t, when the only good brick was brought down, writes on the fd were
still succeeding on the bad bricks. The inflight split-brain check was
marking the write as failure but since the write succeeded on all the
bad bricks, afr_txn_nothing_failed() was set to true and we were
unwinding writev with success to DHT and then catching the failure in
post-op in the background.
Fix:
Don't wind the FOP phase if the write_subvol (which is populated with readable
subvols obtained in pre-op cbk) does not have at least 1 good brick which was up
when the transaction started.
Note: This fix is not related to brick muliplexing. I ran the .t
10 times with this fix and brick-mux enabled without any failures.
Change-Id: I915c9c366aa32cd342b1565827ca2d83cb02ae85
updates: bz#1581548
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
(cherry picked from commit 985a1d15db910e012ddc1dcdc2e333cc28a9968b)
Diffstat (limited to 'xlators/cluster/afr/src/afr-dir-write.h')
0 files changed, 0 insertions, 0 deletions