search for: gd_mgmt_v3_commit_fn

...glusterd_handle_replicate_brick_ops] 0-management: Failed to set extended attribute trusted.add-brick : Operation not supported [Operation not supported] E [MSGID: 106074] [glusterd-brick-ops.c:2565:glusterd_op_add_brick] 0-glusterd: Unable to add bricks E [MSGID: 106123] [glusterd-mgmt.c:311:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed. I was initially using ZFS and noted that ZFS on FreeBSD does not support xattr, so I reverted to using UFS as the storage type for the brick, and still encounter this behavior. I also recompiled the port (again, GlusterFS v3.11.1) with the patch from...

...here seems to indicate the filesystem on the new brick being added doesn't seem to support setting xattrs. Maybe check the new brick again? > E [MSGID: 106074] [glusterd-brick-ops.c:2565:glusterd_op_add_brick] > 0-glusterd: Unable to add bricks > E [MSGID: 106123] [glusterd-mgmt.c:311:gd_mgmt_v3_commit_fn] 0-management: > Add-brick commit failed. > I was initially using ZFS and noted that ZFS on FreeBSD does not support > xattr, so I reverted to using UFS as the storage type for the brick, and > still encounter this behavior. > I also recompiled the port (again, GlusterFS v3.11.1) w...

...nagement: Unable to start brick arbiter-1.network.hoggins.fr:/gluster/thedude [2018-01-29 15:15:55.194823] E [MSGID: 106074] [glusterd-brick-ops.c:2590:glusterd_op_add_brick] 0-glusterd: Unable to add bricks [2018-01-29 15:15:55.194854] E [MSGID: 106123] [glusterd-mgmt.c:312:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed. [2018-01-29 15:15:55.194868] E [MSGID: 106123] [glusterd-mgmt-handler.c:603:glusterd_handle_commit_fn] 0-management: commit failed on operation Add brick However, when I query again : gluster> volume info thedude Volume Name: th...

...glusterd_handle_replicate_brick_ops] 0-management:? Failed to set extended attribute trusted.add-brick : Operation not?? supported [Operation not supported] E [MSGID: 106074] [glusterd-brick-ops.c:2565:glusterd_op_add_brick] 0-glusterd: Unable to add bricks E [MSGID: 106123] [glusterd-mgmt.c:311:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed. I was initially using ZFS and noted that ZFS on FreeBSD does not support xattr, so I reverted to using UFS as the storage type for the brick, and still encounter this behavior. I also recompiled the port (again, GlusterFS v3.11.1) with the patch from ht...

...ls.c:4877:glusterd_brick_start] 0-management: Unable to start brick gluster02ib:/gdata/brick1/scratch [2018-04-25 22:08:55.310275] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks [2018-04-25 22:08:55.310304] E [MSGID: 106123] [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed. [2018-04-25 22:08:55.310316] E [MSGID: 106123] [glusterd-mgmt.c:1427:glusterd_mgmt_v3_commit] 0-management: Commit failed for operation Add brick on local node [2018-04-25 22:08:55.310330] E [MSGID: 106123] [glusterd-mgmt.c:2018:glusterd_mgmt_v3_initiate_all_...

...] 0-management: Unable to start > brick gluster02ib:/gdata/brick1/scratch > [2018-04-25 22:08:55.310275] E [MSGID: 106074] > [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add > bricks > [2018-04-25 22:08:55.310304] E [MSGID: 106123] > [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit > failed. > [2018-04-25 22:08:55.310316] E [MSGID: 106123] > [glusterd-mgmt.c:1427:glusterd_mgmt_v3_commit] 0-management: Commit failed > for operation Add brick on local node > [2018-04-25 22:08:55.310330] E [MSGID: 106123] > [glusterd-mgmt.c:2018:...

...o start >> brick gluster02ib:/gdata/brick1/scratch >> [2018-04-25 22:08:55.310275] E [MSGID: 106074] >> [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add >> bricks >> [2018-04-25 22:08:55.310304] E [MSGID: 106123] >> [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit >> failed. >> [2018-04-25 22:08:55.310316] E [MSGID: 106123] >> [glusterd-mgmt.c:1427:glusterd_mgmt_v3_commit] 0-management: Commit failed >> for operation Add brick on local node >> [2018-04-25 22:08:55.310330] E [MSGID: 106123] >&gt...

...] 0-management: Unable to start > brick gluster02ib:/gdata/brick1/scratch > [2018-04-25 22:08:55.310275] E [MSGID: 106074] > [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add > bricks > [2018-04-25 22:08:55.310304] E [MSGID: 106123] > [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit > failed. > [2018-04-25 22:08:55.310316] E [MSGID: 106123] > [glusterd-mgmt.c:1427:glusterd_mgmt_v3_commit] 0-management: Commit failed > for operation Add brick on local node > [2018-04-25 22:08:55.310330] E [MSGID: 106123] > [glusterd-mgmt.c:2018:...

...lume status show the brick as up and running? -Ravi > [2018-01-29 15:15:55.194823] E [MSGID: 106074] > [glusterd-brick-ops.c:2590:glusterd_op_add_brick] 0-glusterd: Unable > to add bricks > [2018-01-29 15:15:55.194854] E [MSGID: 106123] > [glusterd-mgmt.c:312:gd_mgmt_v3_commit_fn] 0-management: Add-brick > commit failed. > [2018-01-29 15:15:55.194868] E [MSGID: 106123] > [glusterd-mgmt-handler.c:603:glusterd_handle_commit_fn] > 0-management: commit failed on operation Add brick > > > However, when I query again : > > glust...

...ls.c:4877:glusterd_brick_start] 0-management: Unable to start brick gluster02ib:/gdata/brick1/scratch [2018-04-25 20:56:54.391457] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks [2018-04-25 20:56:54.391476] E [MSGID: 106123] [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed. [2018-04-25 20:56:54.391490] E [MSGID: 106123] [glusterd-mgmt-handler.c:603:glusterd_handle_commit_fn] 0-management: commit failed on operation Add brick [2018-04-25 20:58:55.332262] I [MSGID: 106499] [glusterd-handler.c:4349:__glusterd_handle_status_volume]...

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 >

...ls.c:4877:glusterd_brick_start] 0-management: Unable to start brick gluster01ib:/gdata/brick2/scratch [2018-01-10 15:01:16.062715] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks [2018-01-10 15:01:16.062729] E [MSGID: 106123] [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed. [2018-01-10 15:01:16.062741] E [MSGID: 106123] [glusterd-mgmt.c:1427:glusterd_mgmt_v3_commit] 0-management: Commit failed for operation Add brick on local node [2018-01-10 15:01:16.062754] E [MSGID: 106123] [glusterd-mgmt.c:2018:glusterd_mgmt_v3_initiate_all_...

...ls.c:4877:glusterd_brick_start] 0-management: Unable to start brick gluster01ib:/gdata/brick2/scratch [2018-01-10 15:01:16.062715] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks [2018-01-10 15:01:16.062729] E [MSGID: 106123] [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit failed. [2018-01-10 15:01:16.062741] E [MSGID: 106123] [glusterd-mgmt.c:1427:glusterd_mgmt_v3_commit] 0-management: Commit failed for operation Add brick on local node [2018-01-10 15:01:16.062754] E [MSGID: 106123] [glusterd-mgmt.c:2018:glusterd_mgmt_v3_initiate_all_...

On Wed, Apr 11, 2018 at 7:38 PM, Jose Sanchez <josesanc at carc.unm.edu> wrote: > Hi Karthik > > Looking at the information you have provided me, I would like to make sure > that I?m running the right commands. > > 1. gluster volume heal scratch info > If the count is non zero, trigger the heal and wait for heal info count to become zero. > 2. gluster volume

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:

...] 0-management: Unable to start > brick gluster01ib:/gdata/brick2/scratch > [2018-01-10 15:01:16.062715] E [MSGID: 106074] > [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add > bricks > [2018-01-10 15:01:16.062729] E [MSGID: 106123] > [glusterd-mgmt.c:294:gd_mgmt_v3_commit_fn] 0-management: Add-brick commit > failed. > [2018-01-10 15:01:16.062741] E [MSGID: 106123] > [glusterd-mgmt.c:1427:glusterd_mgmt_v3_commit] 0-management: Commit failed > for operation Add brick on local node > [2018-01-10 15:01:16.062754] E [MSGID: 106123] > [glusterd-mgmt.c:2018:...

Hi Jose, Gluster is working as expected. The Distribute-replicated type just means that there are now 2 replica sets and files will be distributed across them. A volume of type Replicate (1xn where n is the number of bricks in the replica set) indicates there is no distribution (all files on the volume will be present on all the bricks in the volume). A volume of type Distributed-Replicate

Hi Nithya This is what i have so far, I have peer both cluster nodes together as replica, from node 1A and 1B , now when i tried to add it , i get the error that it is already part of a volume. when i run the cluster volume info , i see that has switch to distributed-replica. Thanks Jose [root at gluster01 ~]# gluster volume status Status of volume: scratch Gluster process

...terd: Received cli list req [2018-02-02 11:22:32.998693] I [MSGID: 106487] [glusterd-handler.c:1472:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req [2018-02-02 11:23:24.792241] W [common-utils.c:1685:gf_string2boolean] (-->/usr/lib64/glusterfs/3.7.20/xlator/mgmt/glusterd.so(gd_mgmt_v3_commit_fn+0x1f0) [0xffff789b7230] -->/usr/lib64/glusterfs/3.7.20/xlator/mgmt/glusterd.so(glusterd_op_start_volume+0x290) [0xffff789816fc] -->/lib64/libglusterfs.so.0(gf_string2boolean+0x158) [0xffff82e676f0] ) 0-management: argument invalid [Invalid argument] [2018-02-02 11:23:24.967600] I [MSGID: 1061...