search for: thedude

Displaying 10 results from an estimated 10 matches for "thedude".

Replacing a third data node with an arbiter one
2018 Jan 24
4
Replacing a third data node with an arbiter one
Hello, The subject says it all. I have a replica 3 cluster : gluster> volume info thedude ? Volume Name: thedude Type: Replicate Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e Status: Started Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: ngluster-1.network.hoggins.fr:/export/brick/thedude Brick2: ngluster-2...
Replacing a third data node with an arbiter one
2018 Jan 29
2
Replacing a third data node with an arbiter one
Thank you, for that, however I have a problem. Le 26/01/2018 ? 02:35, Ravishankar N a ?crit?: > Yes, you would need to reduce it to replica 2 and then convert it to > arbiter. > 1. Ensure there are no pending heals, i.e. heal info shows zero entries. > 2. gluster volume remove-brick thedude replica 2 > ngluster-3.network.hoggins.fr:/export/brick/thedude force > 3. gluster volume add-brick thedude replica 3 arbiter 1 <IP:brick path > of the new arbiter brick> Removing the current third brick was OK with ??? volume remove-brick thedude replica 2 ngluster-3.network.hoggin...
Replacing a third data node with an arbiter one
2018 Jan 26
0
Replacing a third data node with an arbiter one
On 01/24/2018 07:20 PM, Hoggins! wrote: > Hello, > > The subject says it all. I have a replica 3 cluster : > > gluster> volume info thedude > > Volume Name: thedude > Type: Replicate > Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 3 = 3 > Transport-type: tcp > Bricks: > Brick1: ngluster-1.net...
Replacing a third data node with an arbiter one
2018 Jan 29
0
Replacing a third data node with an arbiter one
...owever I have a problem. > > Le 26/01/2018 ? 02:35, Ravishankar N a ?crit?: >> Yes, you would need to reduce it to replica 2 and then convert it to >> arbiter. >> 1. Ensure there are no pending heals, i.e. heal info shows zero entries. >> 2. gluster volume remove-brick thedude replica 2 >> ngluster-3.network.hoggins.fr:/export/brick/thedude force >> 3. gluster volume add-brick thedude replica 3 arbiter 1 <IP:brick path >> of the new arbiter brick> > Removing the current third brick was OK with > ??? volume remove-brick thedude replica 2 &gt...
Replacing a third data node with an arbiter one
2018 Jan 26
2
Replacing a third data node with an arbiter one
On Fri, Jan 26, 2018 at 7:05 AM, Ravishankar N <ravishankar at redhat.com> wrote: > > > On 01/24/2018 07:20 PM, Hoggins! wrote: > > Hello, > > The subject says it all. I have a replica 3 cluster : > > gluster> volume info thedude > > Volume Name: thedude > Type: Replicate > Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 3 = 3 > Transport-type: tcp > Bricks: > Brick1: ngluster-1.network.hoggins.fr:...
Healing : No space left on device
2018 May 02
3
Healing : No space left on device
...gmt_v3_unlock] (-->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0x22549) [0x7f0047ae2549] -->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0x2bdf0) [0x7f0047aebdf0] -->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0xd8371) [0x7f0047b98371] ) 0-management: Lock for vol thedude not held ??? ??? The message "W [MSGID: 106118] [glusterd-handler.c:6342:__glusterd_peer_rpc_notify] 0-management: Lock not released for rom" repeated 3 times between [2018-05-02 09:45:57.262321] and [2018-05-02 09:46:06.267804] ??? ??? [2018-05-02 09:46:06.267826] W [MSGID: 106118] [glus...
Replacing a third data node with an arbiter one
2018 Jan 26
0
Replacing a third data node with an arbiter one
...Jan 26, 2018 at 7:05 AM, Ravishankar N <ravishankar at redhat.co > m> wrote: > > > > On 01/24/2018 07:20 PM, Hoggins! wrote: > > > > Hello, > > > > The subject says it all. I have a replica 3 cluster : > > > > gluster> volume info thedude > > > > Volume Name: thedude > > Type: Replicate > > Volume ID: bc68dfd3-94e2-4126-b04d-77b51ec6f27e > > Status: Started > > Snapshot Count: 0 > > Number of Bricks: 1 x 3 = 3 > > Transport-type: tcp > > Bricks: &...
Healing : No space left on device
2018 May 02
0
Healing : No space left on device
...r/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0x22549) > [0x7f0047ae2549] > -->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0x2bdf0) > [0x7f0047aebdf0] > -->/usr/lib64/glusterfs/3.12.9/xlator/mgmt/glusterd.so(+0xd8371) > [0x7f0047b98371] ) 0-management: Lock for vol thedude not held > ??? ??? The message "W [MSGID: 106118] > [glusterd-handler.c:6342:__glusterd_peer_rpc_notify] 0-management: Lock > not released for rom" repeated 3 times between [2018-05-02 > 09:45:57.262321] and [2018-05-02 09:46:06.267804] > ??? ??? [2018-05-02 09:46:06.267826...
How to make sure self-heal backlog is empty ?
2017 Dec 19
3
How to make sure self-heal backlog is empty ?
....network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/rom <gfid:52b09fb6-78da-46db-af0e-e6a16194a977> Status: Connected Number of entries: 1 Brick ngluster-1.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/thedude <gfid:4b1f4d9b-f2d8-4a50-83f7-3f014fe0b9f6> Status: Connected Number of entries: 1 Brick ngluster-3.network.hoggins.fr:/export/brick/thedude Status: Connected...
How to make sure self-heal backlog is empty ?
2017 Dec 19
0
How to make sure self-heal backlog is empty ?
....network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/rom <gfid:52b09fb6-78da-46db-af0e-e6a16194a977> Status: Connected Number of entries: 1 Brick ngluster-1.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/thedude <gfid:4b1f4d9b-f2d8-4a50-83f7-3f014fe0b9f6> Status: Connected Number of entries: 1 Brick ngluster-3.network.hoggins.fr:/export/brick/thedude Status: Connected...