|
Hi All, Found solution, it was a syntax issue in the mount of my volumes. Now this is fixed. PM From: gluster-users-bounces@xxxxxxxxxxx [mailto:gluster-users-bounces@xxxxxxxxxxx]
On Behalf Of Janvre, Pierre-Marie (Agoda) Hi All, I have a Gluster deployment on version 3.6.1 with 6 volumes, each of them with 2 bricks. After I create the volumes, I can't start them, excluding the last one as each of them shows it sees the volume ID of the last one as you can see below: [root@node_1 ~]# gluster volume info all Volume Name: volume_b Type: Replicate Volume ID: 72b7c697-a949-4cad-98e7-5592c2c4a46b Status: Stopped Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: node_1:/brick_1b Brick2: node_2:/brick_2b Volume Name: volume_c Type: Replicate Volume ID: 6e8eb692-f07c-40bf-a0d3-ba42941fac04 Status: Stopped Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: node_1:/brick_1c Brick2: node_2:/brick_2c Volume Name: volume_d Type: Replicate Volume ID: c0c502de-52c5-4838-8b8d-c1bedd9d995e Status: Stopped Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: node_1:/brick_1d Brick2: node_2:/brick_2d Volume Name: volume_e Type: Replicate Volume ID: 6b35faf6-6a1e-41dd-8024-1458a693d87c Status: Stopped Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: node_1:/brick_1e Brick2: node_2:/brick_2e Volume Name: volume_f Type: Replicate Volume ID: f60824e6-a780-491f-9e2d-9511b15802e1 Status: Stopped Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: node_1:/brick_1f Brick2: node_2:/brick_2f Volume Name: volume_g Type: Replicate Volume ID: 566425fa-9ec2-4c97-ad36-62f077e0adb9 Status: Created Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: node_1:/brick_1g Brick2: node_2:/brick_2g [root@node_1 ~]# gluster volume start volume_b volume start: volume_b: failed: Volume id mismatch for brick node_1:/brick_1b. Expected volume id 72b7c697-a949-4cad-98e7-5592c2c4a46b, volume id 566425fa-9ec2-4c97-ad36-62f077e0adb9 found [root@node_1 ~]# gluster volume start volume_c volume start: volume_c: failed: Volume id mismatch for brick node_1:/brick_1c. Expected volume id 6e8eb692-f07c-40bf-a0d3-ba42941fac04, volume id 566425fa-9ec2-4c97-ad36-62f077e0adb9 found [root@node_1 ~]# gluster volume start volume_d volume start: volume_d: failed: Volume id mismatch for brick node_1:/brick_1d. Expected volume id c0c502de-52c5-4838-8b8d-c1bedd9d995e, volume id 566425fa-9ec2-4c97-ad36-62f077e0adb9 found [root@node_1 ~]# gluster volume start volume_e volume start: volume_e: failed: Volume id mismatch for brick node_1:/brick_1e. Expected volume id 6b35faf6-6a1e-41dd-8024-1458a693d87c, volume id 566425fa-9ec2-4c97-ad36-62f077e0adb9 found [root@node_1 ~]# gluster volume start volume_f volume start: volume_f: failed: Volume id mismatch for brick node_1:/brick_1f. Expected volume id f60824e6-a780-491f-9e2d-9511b15802e1, volume id 566425fa-9ec2-4c97-ad36-62f077e0adb9 found [root@node_1 ~]# gluster volume start volume_g volume start: volume_g: success Any idea why this occurs and how to fix it ? On my previous deployment of v 3.4.2, I didn’t have that problem. Thank you PM This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply
email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and
from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
