Description of problem: -------------------------- when we issue a volume info from a node in the cluster, which doesnt host any of the bricks of that volume, we see ambiguous data as below However the same is not seen when issued from a node which is hosting one of the bricks(in below case either from dhcp35-140/38/184) This is reproducible always Also, this is seen when the volume is created only Once started, you don't see this vol info from node which doesnt host brick ========================================== Volume Name: rep3-8 Type: Replicate Volume ID: ecff9a6e-0c14-4124-acfb-e41aff40debf Status: Created Snapshot Count: 0 Xlator 1: BD Capability 1: thin Capability 2: offload_copy Capability 3: offload_snapshot Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: dhcp35-140.lab.eng.blr.redhat.com:/gluster/brick8/rep3-8 Brick1 VG: Brick2: dhcp35-38.lab.eng.blr.redhat.com:/gluster/brick8/rep3-8 Brick2 VG: Brick3: dhcp35-184.lab.eng.blr.redhat.com:/gluster/brick8/rep3-8 Brick3 VG: Options Reconfigured: transport.address-family: inet nfs.disable: on performance.client-io-threads: off volinfo from node which hosts brick ===================================== Volume Name: rep3-8 Type: Replicate Volume ID: ecff9a6e-0c14-4124-acfb-e41aff40debf Status: Created Snapshot Count: 0 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: dhcp35-140.lab.eng.blr.redhat.com:/gluster/brick8/rep3-8 Brick2: dhcp35-38.lab.eng.blr.redhat.com:/gluster/brick8/rep3-8 Brick3: dhcp35-184.lab.eng.blr.redhat.com:/gluster/brick8/rep3-8 Options Reconfigured: transport.address-family: inet nfs.disable: on performance.client-io-threads: off I did go through some volfiles and found a descrepency here [root@dhcp35-140 bricks]# cat dhcp35-140.lab.eng.blr.redhat.com\:-gluster-brick8-rep3-8 uuid=c63a0191-c6b0-4073-a0b0-f5ca0cf3f128 hostname=dhcp35-140.lab.eng.blr.redhat.com path=/gluster/brick8/rep3-8 real_path=/gluster/brick8/rep3-8 listen-port=0 rdma.listen-port=0 decommissioned=0 brick-id=rep3-8-client-0 mount_dir=/rep3-8 snap-status=0 brick-fsid=64810 [root@dhcp35-140 bricks]# [root@dhcp35-140 bricks]# cat /var/lib/glusterd/vols/rep3-8/bricks/dhcp35-140.lab.eng.blr.redhat.com\:-gluster-brick8-rep3-8 uuid=c63a0191-c6b0-4073-a0b0-f5ca0cf3f128 hostname=dhcp35-140.lab.eng.blr.redhat.com path=/gluster/brick8/rep3-8 real_path=/gluster/brick8/rep3-8 listen-port=0 rdma.listen-port=0 decommissioned=0 brick-id=rep3-8-client-0 mount_dir=/rep3-8 snap-status=0 brick-fsid=64810 ------------------>From node which hosts volume [root@dhcp35-140 bricks]# [root@dhcp35-218 bricks]# cat /var/lib/glusterd/vols/rep3-8/bricks/dhcp35-140.lab.eng.blr.redhat.com:-gluster-brick8-rep3-8 uuid=c63a0191-c6b0-4073-a0b0-f5ca0cf3f128 hostname=dhcp35-140.lab.eng.blr.redhat.com path=/gluster/brick8/rep3-8 real_path=/gluster/brick8/rep3-8 listen-port=0 rdma.listen-port=0 decommissioned=0 brick-id=rep3-8-client-0 mount_dir=/rep3-8 snap-status=0 brick-fsid=0 ------------------>From node which doesnt host volume [root@dhcp35-218 bricks]# Version-Release number of selected component (if applicable): ------------------------------ 3.12.2-18 How reproducible: ================= always Steps to Reproduce: 1.have a 6 node cluster 2.create a 1x3 or arbiter volume with bricks from only 3 of the 6 nodes 3.issue volume info from any node which hosts the brick of the volume 4. issue vol info from any node which *doesnt* host brick of the volume You can notice the discrepancy.
Sanju has started working on this. Moving the state to Assigned.
upstream patch: https://review.gluster.org/21336
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3827