search for: prevalidation

...usterd-utils.c:6064:glusterd_new_brick_validate] 0-management: Brick: gluster02ib:/gdata/brick1/scratch not available. Brick may be containing or be contained by an existing brick [2018-04-25 22:09:11.678184] W [MSGID: 106122] [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick prevalidation failed. [2018-04-25 22:09:11.678200] E [MSGID: 106122] [glusterd-mgmt-handler.c:337:glusterd_handle_pre_validate_fn] 0-management: Pre Validation failed on operation Add brick [root at gluster02 glusterfs]# gluster volume status scratch Status of volume: scratch Gluster process...

...erd_new_brick_validate] 0-management: Brick: > gluster02ib:/gdata/brick1/scratch not available. Brick may be containing or > be contained by an existing brick > [2018-04-25 22:09:11.678184] W [MSGID: 106122] > [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick > prevalidation failed. > [2018-04-25 22:09:11.678200] E [MSGID: 106122] > [glusterd-mgmt-handler.c:337:glusterd_handle_pre_validate_fn] 0-management: > Pre Validation failed on operation Add brick > [root at gluster02 glusterfs]# gluster volume status scratch > Status of volume: scratch > Gluste...

...te] 0-management: Brick: >> gluster02ib:/gdata/brick1/scratch not available. Brick may be containing or >> be contained by an existing brick >> [2018-04-25 22:09:11.678184] W [MSGID: 106122] >> [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick >> prevalidation failed. >> [2018-04-25 22:09:11.678200] E [MSGID: 106122] >> [glusterd-mgmt-handler.c:337:glusterd_handle_pre_validate_fn] 0-management: >> Pre Validation failed on operation Add brick >> [root at gluster02 glusterfs]# gluster volume status scratch >> Status of volume:...

...usterd-utils.c:6064:glusterd_new_brick_validate] 0-management: Brick: gluster02ib:/gdata/brick1/scratch not available. Brick may be containing or be contained by an existing brick [2018-04-25 21:02:07.464395] W [MSGID: 106122] [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick prevalidation failed. [2018-04-25 21:02:07.464414] E [MSGID: 106122] [glusterd-mgmt-handler.c:337:glusterd_handle_pre_validate_fn] 0-management: Pre Validation failed on operation Add brick [2018-04-25 21:04:56.198662] E [MSGID: 106452] [glusterd-utils.c:6064:glusterd_new_brick_validate] 0-management: Brick: glu...

...erd_new_brick_validate] 0-management: Brick: > gluster02ib:/gdata/brick1/scratch not available. Brick may be containing or > be contained by an existing brick > [2018-04-25 22:09:11.678184] W [MSGID: 106122] > [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick > prevalidation failed. > [2018-04-25 22:09:11.678200] E [MSGID: 106122] > [glusterd-mgmt-handler.c:337:glusterd_handle_pre_validate_fn] 0-management: > Pre Validation failed on operation Add brick > [root at gluster02 glusterfs]# gluster volume status scratch > Status of volume: scratch > Gluste...

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

...09.876763] E [MSGID: 106451] > [glusterd-utils.c:6207:glusterd_is_path_in_use] 0-management: > /gdata/brick2/scratch is already part of a volume [File exists] > [2018-01-10 15:01:09.876807] W [MSGID: 106122] > [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick > prevalidation failed. > [2018-01-10 15:01:09.876822] E [MSGID: 106122] > [glusterd-mgmt.c:884:glusterd_mgmt_v3_pre_validate] 0-management: Pre > Validation failed for operation Add brick on local node > [2018-01-10 15:01:09.876834] E [MSGID: 106122] > [glusterd-mgmt.c:2009:glusterd_mgmt_v3_initiat...

...d-brick gv0 replica 3 192.168.3.31:/export/gfs/brick volume add-brick: failed: Pre Validation failed on 192.168.3.31. Please check log file for details. On 192.168.3.31 [2024-01-03 17:49:24.734669 +0000] W [MSGID: 106121] [glusterd-mgmt.c:161:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick prevalidation failed. [2024-01-03 17:49:24.734683 +0000] E [MSGID: 106121] [glusterd-mgmt-handler.c:321:glusterd_handle_pre_validate_fn] 0-management: Pre Validation failed on operation Add brick Commands on 192.168.3.31 all report Unable to find volume: gv0/ or Volume gv0 does not exist Been fighting this...

...t is 2 [2018-01-10 15:01:09.876763] E [MSGID: 106451] [glusterd-utils.c:6207:glusterd_is_path_in_use] 0-management: /gdata/brick2/scratch is already part of a volume [File exists] [2018-01-10 15:01:09.876807] W [MSGID: 106122] [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick prevalidation failed. [2018-01-10 15:01:09.876822] E [MSGID: 106122] [glusterd-mgmt.c:884:glusterd_mgmt_v3_pre_validate] 0-management: Pre Validation failed for operation Add brick on local node [2018-01-10 15:01:09.876834] E [MSGID: 106122] [glusterd-mgmt.c:2009:glusterd_mgmt_v3_initiate_all_phases] 0-managemen...

...t is 2 [2018-01-10 15:01:09.876763] E [MSGID: 106451] [glusterd-utils.c:6207:glusterd_is_path_in_use] 0-management: /gdata/brick2/scratch is already part of a volume [File exists] [2018-01-10 15:01:09.876807] W [MSGID: 106122] [glusterd-mgmt.c:188:gd_mgmt_v3_pre_validate_fn] 0-management: ADD-brick prevalidation failed. [2018-01-10 15:01:09.876822] E [MSGID: 106122] [glusterd-mgmt.c:884:glusterd_mgmt_v3_pre_validate] 0-management: Pre Validation failed for operation Add brick on local node [2018-01-10 15:01:09.876834] E [MSGID: 106122] [glusterd-mgmt.c:2009:glusterd_mgmt_v3_initiate_all_phases] 0-managemen...

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