[Bugs] [Bug 1647506] glusterd_brick_start wrongly discovers already-running brick

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1647506



--- Comment #6 from patrice at buleon.net ---
And gluster v info result :

[root at pb-gluster-ope-0 /]# gluster v info

Volume Name: glusterPGSQL
Type: Replicate
Volume ID: 322d4e1f-483a-4dae-8a3c-8f6fbc51dd57
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: pilot-0:/mnt/glusterPGSQL/1
Brick2: pilot-1:/mnt/glusterPGSQL/1
Brick3: pilot-2:/mnt/glusterPGSQL/1
Options Reconfigured:
cluster.self-heal-daemon: enable
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off

Volume Name: glustervol1
Type: Replicate
Volume ID: 10dca74f-2cf6-476c-89e1-69e6a67a7bde
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: pilot-0:/local/glusterV0/1
Brick2: pilot-1:/local/glusterV0/1
Brick3: pilot-2:/local/glusterV0/1
Options Reconfigured:
cluster.self-heal-daemon: enable
transport.address-family: inet
nfs.disable: on
performance.client-io-threads: off

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.