Hello, we have a gluster volume (replica 3). We removed one node and detached the peer, running gluster6 on ubuntu 18.04. gluster v remove-brick gv1 replica 2 c3:/gluster/brick force gluster peer detach c3 We installed ubuntu 20.04 and gluster9 We than had a volume with two nodes up ad running. We replaced the HDs with SSDs reformated the disk with xfs. Then we did a gluster peer probe c3 to add the brick, that works "gluster peer status" and "gluster pool list" is showing the brick. Trying to add the brick with: gluster v add-brick gv1 replica 3 c3:/gluster/brick gives us the following error: volume add-brick: failed: Pre Validation failed on c3. Please check log file for details. But we only found the same errormesage in the log. Then we checked the status of the volume and got: gluster v status gv1 Staging failed on c3. Error: Volume gv1 does not exist So the volume crashes. A "gluster v info" is showing: root@fs002010:~# gluster v info Volume Name: gv1 Type: Replicate Volume ID: b93f1432-083b-42c1-870a-1e9faebc4a7d Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: c1:/gluster/brick Brick2: c2:/gluster/brick Options Reconfigured: nfs.disable: on As soon as we detach c3 the volume status is OK, without restarting glusterd What might be the problem? Adding gluster9 to a gluster6 volume? The name resolution is using /etc/hosts so all 3 hosts in all 3 /etc/hosts file and can be reached via ping. Any help? Stefan
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
