Hi Zack,
As the bricks had already been used before, gluster doesn't allow to
create volume with same brick path until you use "force" at the end of
the command. As you are doing performance testing i would recommend to
clean the bricks and issue the same command.
. sudo gluster volume create gluster1 transport tcp
cyan:/gluster/ssd1/brick1*new* green:/gluster/ssd1/brick2*new*
red:/gluster/ssd1/brick3*new* pink:/gluster/ssd1/brick4*new
*
for time being this will solve the your problem.
Thanks & Regards
Karan Sandha
On 01/05/2017 05:53 AM, Zack Boll wrote:
In performance testing a striped 4 volume, I appeared to have crashed
glusterfs using version 3.8.7 on Ubuntu 16.04. I then stopped the
volume and deleted it. I am now having trouble creating a new volume,
below is output
sudo gluster volume create gluster1 transport tcp
cyan:/gluster/ssd1/brick1 green:/gluster/ssd1/brick2
red:/gluster/ssd1/brick3 pink:/gluster/ssd1/brick4
volume create: gluster1: failed: Staging failed on green. Error:
/gluster/ssd1/brick2 is already part of a volume
Staging failed on pink. Error: /gluster/ssd1/brick4 is already part of
a volume
Staging failed on cyan. Error: /gluster/ssd1/brick1 is already part of
a volume
Staging failed on red. Error: /gluster/ssd1/brick3 is already part of
a volume
sudo gluster volume info
No volumes present
Any ideas on how to fix this?
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
