[Gluster-users] command failure

[Thing]

I dont seem to have a consistant cluster,

how do I get rid of 192.168.1.1 which shouldnt be there?  deatch wont work,
is there a file I can edit by hand?

=========
[root at ipa1 salt]#  salt 'glusterp1.graywitch.co.nz' cmd.run "gluster peer
status"
glusterp1.graywitch.co.nz:
    Number of Peers: 1

    Hostname: glusterp3.graywitch.co.nz
    Uuid: 5d59b704-e42f-46c6-8c14-cf052c489292
    State: Peer in Cluster (Connected)
[root at ipa1 salt]#  salt 'glusterp3.graywitch.co.nz' cmd.run "gluster peer
status"
glusterp3.graywitch.co.nz:
    Number of Peers: 1

    Hostname: glusterp1.graywitch.co.nz
    Uuid: 4ece8509-033e-48d1-809f-2079345caea2
    State: Accepted peer request (Connected)
[root at ipa1 salt]#  salt 'glusterp2.graywitch.co.nz' cmd.run "gluster peer
status"
glusterp2.graywitch.co.nz:
    Number of Peers: 2

    Hostname: 192.168.1.1
    Uuid: 4ece8509-033e-48d1-809f-2079345caea2
    State: Establishing Connection (Disconnected)
    Other names:
    glusterp1.graywitch.co.nz

    Hostname: glusterp3.graywitch.co.nz
    Uuid: 5d59b704-e42f-46c6-8c14-cf052c489292
    State: Accepted peer request (Disconnected)
[root at ipa1 salt]#

On 14 December 2015 at 14:10, Thing <thing.thing at gmail.com> wrote:

> Hi,
>
> No its mounted fine.
>
> --edit--
>
> data1 not data01, doh....
>
>
>
> On 14 December 2015 at 13:53, Lindsay Mathieson <
> lindsay.mathieson at gmail.com> wrote:
>
>> On 14/12/15 10:34, Thing wrote:
>>
>> I am trying to setup a replication across 3 servers, for some reason I
>> get a failure,
>>
>> /data1 is my 120gb test volume, (I am waiting on the arrival of 3 x 1tb
>> disks)
>>
>> The failure I get is,
>>
>> =====
>> [root at ipa1 salt]# salt glusterp1.graywitch.co.nz cmd.run "gluster volume
>> create glustervol01 replica 3 glusterp1.graywitch.co.nz:/data01
>> glusterp2.graywitch.co.nz:/data01 glusterp3.graywitch.co.nz:/data01"
>> glusterp1.graywitch.co.nz:
>>     volume create: glustervol01: failed: The brick
>> glusterp1.graywitch.co.nz:/data01 is being created in the root
>> partition. It is recommended that you don't use the system's root partition
>> for storage backend. Or use 'force' at the end of the command if you want
>> to override this behavior.
>> =====
>>
>>
>>
>> Have you confirmed that /data01 is actually mounted on glusterp1? I
>> generated this error just yesterday in testing and it turned out my mount
>> wasn't :)
>>
>> easy check - on glusterp1:
>>
>>   df -h|grep data01
>>
>>
>>
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151214/00d7c80c/attachment.html>