search for: glusterd_op_add_brick

...ks] 0-management: type is set 2, need to change it E [MSGID: 106054] [glusterd-utils.c:12974: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 enco...

Apologies for the delay! >From the logs: [2017-05-31 13:06:35.839780] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start brick 156.125.102.103:/data/br0/vm0 [2017-05-31 13:06:35.839869] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks This looks like in serv3 the newly added brick failed to come up. You'd have to look at the same brick log file on serv3 to see what was the reason. As a workaround, does gluster v start <volname> force bring up this brick now? As far as glusterd config...

...t extended attribute trusted.add-brick : Operation not > supported [Operation not supported] The log 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 bric...

...cess for brick /gluster/thedude [2018-01-29 15:15:55.194678] E [MSGID: 106005] [glusterd-utils.c:5947:glusterd_brick_start] 0-management: 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-man...

...the delay! > > From the logs: > > [2017-05-31 13:06:35.839780] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start] > 0-management: Unable to start brick 156.125.102.103:/data/br0/vm0 > > > [2017-05-31 13:06:35.839869] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] > 0-glusterd: Unable to add bricks > > This looks like in serv3 the newly added brick failed to come up. You'd > have to look at the same brick log file on serv3 to see what was the > reason. As a workaround, does gluster v start <volname> force bring up this > brick n...

...lica to the cluster Apologies for the delay! >From the logs: [2017-05-31 13:06:35.839780] E [MSGID: 106005] [glusterd-utils.c:4877:glusterd_brick_start] 0-management: Unable to start brick 156.125.102.103:/data/br0/vm0 [2017-05-31 13:06:35.839869] E [MSGID: 106074] [glusterd-brick-ops.c:2493:glusterd_op_add_brick] 0-glusterd: Unable to add bricks This looks like in serv3 the newly added brick failed to come up. You'd have to look at the same brick log file on serv3 to see what was the reason. As a workaround, does gluster v start <volname> force bring up this brick now? As far as glusterd config...

...cks] 0-management: type is set 2, need to change it E [MSGID: 106054] [glusterd-utils.c:12974: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 encounte...

...] 0-pmap: adding brick /gdata/brick1/scratch.rdma on port 49153 [2018-04-25 22:08:55.310231] E [MSGID: 106005] [glusterd-utils.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...

...data/brick1/scratch.rdma on port 49153 > [2018-04-25 22:08:55.310231] E [MSGID: 106005] > [glusterd-utils.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...

...rdma on port 49153 >> [2018-04-25 22:08:55.310231] E [MSGID: 106005] >> [glusterd-utils.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...

...data/brick1/scratch.rdma on port 49153 > [2018-04-25 22:08:55.310231] E [MSGID: 106005] > [glusterd-utils.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...

...> start brick arbiter-1.network.hoggins.fr:/gluster/thedude You need to find why is this so. What does the arbiter brick log say? Does gluster volume 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:...

...] 0-pmap: adding brick /gdata/brick1/scratch.rdma on port 49153 [2018-04-25 20:56:54.391401] E [MSGID: 106005] [glusterd-utils.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 op...

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 >

...] 0-pmap: adding brick /gdata/brick2/scratch.rdma on port 49155 [2018-01-10 15:01:16.062673] E [MSGID: 106005] [glusterd-utils.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...

...] 0-pmap: adding brick /gdata/brick2/scratch.rdma on port 49155 [2018-01-10 15:01:16.062673] E [MSGID: 106005] [glusterd-utils.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...

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:

...data/brick2/scratch.rdma on port 49155 > [2018-01-10 15:01:16.062673] E [MSGID: 106005] > [glusterd-utils.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...

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