diff options
author | Sanju Rakonde <srakonde@redhat.com> | 2019-11-26 17:03:44 +0530 |
---|---|---|
committer | MOHIT AGRAWAL <moagrawa@redhat.com> | 2019-12-05 08:37:24 +0000 |
commit | dc757b2c97f5917885db76c62fa4fb429ae7b9ab (patch) | |
tree | 14b9f1b6cb7ced74360fd1dea50181dea4640615 /libglusterfs/src/mem-pool.c | |
parent | 6015ab7d8b37388e836f36a315af54f019839d91 (diff) |
glusterd: set xaatrs after checking the brick order
Problem: When volume creation fails complaining about
the bricks from same hosts for replica volumes, the
bricks can't be re-used to create any volume without
using force at the end. It says, brick is already part
of a volume.
Reason: When volume create opeartion issued, we set
xattrs on the bricks. If the transaction fails in later
checks, the xattrs will remain on the brick. When the
brick is re-used, by looking at the xattrs, glusterd
thinks it is already part of volume.
Solution: Check the brick order for replica and disperse
volumes before setting the xattrs.
fixes: bz#1776801
Change-Id: I44a971b37f520e5a20dc9fad6520286d315063b9
Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
Diffstat (limited to 'libglusterfs/src/mem-pool.c')
0 files changed, 0 insertions, 0 deletions