diff options
| author | Ravishankar N <ravishankar@redhat.com> | 2020-08-19 11:14:25 +0530 |
|---|---|---|
| committer | Rinku Kothiya <rkothiya@redhat.com> | 2020-08-21 10:42:33 +0000 |
| commit | f120311737cf681c36423d8551e2e218509cd5f7 (patch) | |
| tree | 78d38154c8ec614bdad39c726eff3e0638f0b38c /doc/release-notes/8.1.md | |
| parent | 4398db9d70f34e9a8af88fe3de564a906db7b182 (diff) | |
afr: add null check for thin-arbiter gfid.
Problem:
Lookup/creation of thin-arbiter ID file happens in background during
mounting. On new volumes, if the ID file creation is in progress, and a
FOP fails on data brick, a post-op (xattrop) is attemtped on TA. Since
the TA file's gfid is null at this point, the ASSERT checks in protocol/
client causes a crash.
Fix:
Given that we decided to do Lookup/creation of thin-arbiter in
background, fail the other AFR FOPS on TA if the ID file's gfid is null
instead of winding it down to protocol/client.
Also remove afr_changelog_thin_arbiter_post_op() which seems to be dead
code.
Updates: #763
Change-Id: I70dc666faf55cc5c8f7cf8e7d36085e4fa399c4d
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
(cherry picked from commit f9b5074394e3d2f3b6728aab97230ba620879426)
Diffstat (limited to 'doc/release-notes/8.1.md')
0 files changed, 0 insertions, 0 deletions