Pre Validation failed on 192.168.3.31. Volume gv1 does not exist

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Background ....

Three Fedora servers, 34 and two 37.  Upgraded on of the servers to Fedora 39.  For some reason the 39 server would not rejoin the party.  So I deleted the Fedora 39 server, manually tidied up the brick on Fed39 (192.168.3.31).  I run peer probe and all three serves are connected.

Now the volume displays [FQDN switched to IPs] as below. So I think I just need to add the brick back

gluster volume add-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 for a while now and very very stuck.  Note: I added a new volume gv1 and all was good (initially - broke it repo'ing the real problem)
 

Volume Name: gv0
Type: Replicate
Volume ID: 6a87dc01-09b5-4040-8db7-18b5dc3808f2
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 192.168.3.8:/export/gfs/brick
Brick2: 192.168.3.18:/export/gfs/brick
Options Reconfigured:
transport.address-family: inet
storage.fips-mode-rchecksum: on
nfs.disable: on
performance.client-io-threads: off
auth.allow: 192.168.204.31,192.168.204.18

Peers status are

Fedora 35

gluster peer status
Number of Peers: 2

Hostname: 192.168.3.8
Uuid: 445195bd-d071-48c1-8785-1d455cc447c5
State: Peer in Cluster (Connected)
Other names:
192.168.3.8

Hostname: 192.168.3.31
Uuid: 7e085d9f-a0f9-4ed6-a850-44b6ed991081
State: Peer in Cluster (Connected)


Fedora 39

gluster peer status
Number of Peers: 2

Hostname: 192.168.3.18
Uuid: 7738f786-b35f-4be8-8fd9-e609c11f2b72
State: Peer in Cluster (Connected)
Other names:
192.168.3.18

Hostname: 192.168.3.8
Uuid: 445195bd-d071-48c1-8785-1d455cc447c5
State: Peer in Cluster (Connected)
Other names:
192.168.3.8

Fedora 37
 gluster peer status
Number of Peers: 2

Hostname: 192.168.3.18
Uuid: 7738f786-b35f-4be8-8fd9-e609c11f2b72
State: Peer in Cluster (Connected)
Other names:
192.168.3.18

Hostname: 192.168.3.31
Uuid: 7e085d9f-a0f9-4ed6-a850-44b6ed991081
State: Peer in Cluster (Connected)




-- 
Paul Watson
Oninit www.oninit.com
Tel: +1 913 364 0360
Cell: +1 913 387 7529

Oninit® is a registered trademark of Oninit LLC

If you want to improve, be content to be thought foolish and stupid
Failure is not as frightening as regret
________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux