Hi, I discovered this strange situation when I rebooted one of the nodes. After the reboot I removed the brick on node 2, but for some reason it seems like that information didn't each node 1. Any idea what could have gone wrong and how to troubleshoot? Up until now I've never seen that the nodes disagree on peer status and volume definitions. Node 1: Correct volume definition but no peers available. IP: 10.32.0.32 # gluster peer status Number of Peers: 0 # gluster volume info Volume Name: c_glstr Type: Replicate Volume ID: d1e56a0c-fdbe-47cf-8f3d-edd54d1c73e2 Status: Started Number of Bricks: 1 x 2 = 2 Transport-type: tcp Bricks: Brick1: 10.32.0.48:/opt/lvmdir/c2/brick Brick2: 10.32.0.64:/opt/lvmdir/c2/brick Options Reconfigured: network.ping-timeout: 4 Node 2 ---------- At least the peer is connected, but a brick is missing from the volume. IP: 10.32.0.64 # gluster peer status Number of Peers: 1 Hostname: 10.32.0.48 Uuid: db59a429-9f0f-4512-8d3a-e19b54c88370 State: Accepted peer request (Connected) # gluster volume info Volume Name: c_glstr Type: Distribute Volume ID: d1e56a0c-fdbe-47cf-8f3d-edd54d1c73e2 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.32.0.48:/opt/lvmdir/c2/brick Options Reconfigured: network.ping-timeout: 4 Regards Andreas _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
