Displaying 6 results from an estimated 6 matches for "myvol1".
Did you mean:
myvol
2018 Feb 06
1
strange hostname issue on volume create command with famous Peer in Cluster state error message
...pt-get install glusterfs-server
root at pri:~# apt-mark hold glusterfs*
root at pri:~# reboot now
root at pri:~# gluster peer probe sec.ostechnix.lan
peer probe: success.
root at pri:~# gluster peer probe third.ostechnix.lan
peer probe: success.
root at pri:/var/log/glusterfs# gluster volume create myvol1 replica 3 transport tcp pri.ostechnix.lan:/gluster/brick1/mpoint1 sec.ostechnix.lan:/gluster/brick1/mpoint1 third.ostechnix.lan:/gluster/brick1/mpoint1 force
volume create: myvol1: success: please start the volume to access data
and volume created
root at pri:~# gluster volume list
myvol1
Thank...
2018 Feb 06
0
strange hostname issue on volume create command with famous Peer in Cluster state error message
...> node2 hostname
> third.ostechnix.lan
>
>
> 51.15.77.14 pri.ostechnix.lan pri
> 51.15.90.60 sec.ostechnix.lan sec
> 163.172.151.120 third.ostechnix.lan third
>
> volume create command is
>
> root at pri:/var/log/glusterfs# gluster volume create myvol1 replica 2
> transport tcp pri.ostechnix.lan:/gluster/brick1/mpoint1
> sec.ostechnix.lan:/gluster/brick1/mpoint1 force
> Replica 2 volumes are prone to split-brain. Use Arbiter or Replica 3 to
> avoid this. See: https://gluster.readthedocs.io/en/latest/Administrator%
> 20Guide/Split%...
2018 Feb 06
5
strange hostname issue on volume create command with famous Peer in Cluster state error message
....ostechnix.lan
node2 hostname
sec.ostechnix.lan
node2 hostname
third.ostechnix.lan
51.15.77.14 pri.ostechnix.lan pri
51.15.90.60 sec.ostechnix.lan sec
163.172.151.120 third.ostechnix.lan third
volume create command is
root at pri:/var/log/glusterfs# gluster volume create myvol1 replica 2 transport tcp pri.ostechnix.lan:/gluster/brick1/mpoint1 sec.ostechnix.lan:/gluster/brick1/mpoint1 force
Replica 2 volumes are prone to split-brain. Use Arbiter or Replica 3 to avoid this. See: https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Split%20brain%20and%20ways%20to%...
2013 Jan 03
2
"Failed to perform brick order check,..."
Hi guys:
I have just installed gluster on a single instance, and the command:
gluster volume create gv0 replica 2 server.n1:/export/brick1
server.n1:/export/brick2
returns with:
"Failed to perform brick order check... do you want to continue ..? y/N"?
What is the meaning of this error message, and why does brick order matter?
--
Jay Vyas
http://jayunit100.blogspot.com
2018 Feb 06
0
strange hostname issue on volume create command with famous Peer in Cluster state error message
...> node2 hostname
> third.ostechnix.lan
>
>
> 51.15.77.14 pri.ostechnix.lan pri
> 51.15.90.60 sec.ostechnix.lan sec
> 163.172.151.120 third.ostechnix.lan third
>
> volume create command is
>
> root at pri:/var/log/glusterfs# gluster volume create myvol1 replica 2
> transport tcp pri.ostechnix.lan:/gluster/brick1/mpoint1
> sec.ostechnix.lan:/gluster/brick1/mpoint1 force
> Replica 2 volumes are prone to split-brain. Use Arbiter or Replica 3 to
> avoid this. See:
> https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Split%20...
2018 Feb 07
2
Ip based peer probe volume create error
On 8/02/2018 4:45 AM, Gaurav Yadav wrote:
> After seeing command history, I could see that you have 3 nodes, and
> firstly you are peer probing 51.15.90.60? and 163.172.151.120 from?
> 51.15.77.14
> So here itself you have 3 node cluster, after all this you are going
> on node 2 and again peer probing 51.15.77.14.
> ?Ideally it should work, with above steps, but due to some