Description of problem: ====================== When a new volume in created and "gluster volume info <volume_name> " is executed, it outputs information about the BD Xlator. root@mia [Jul-04-2014-11:27:45] >gluster v info Volume Name: rep Type: Distributed-Replicate Volume ID: 253bf0b1-617a-496e-80f3-302904f5a9fa Status: Created Snap Volume: no Xlator 1: BD Capability 1: thin Capability 2: offload_copy Capability 3: offload_snapshot Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: rhs-client11:/rhs/device0/rep_brick1 Brick1 VG: Brick2: rhs-client12:/rhs/device0/rep_brick2 Brick2 VG: Brick3: rhs-client13:/rhs/device0/rep_brick3 Brick3 VG: Brick4: rhs-client14:/rhs/device0/rep_brick4 Brick4 VG: Options Reconfigured: performance.readdir-ahead: on auto-delete: disable snap-max-soft-limit: 90 snap-max-hard-limit: 256 root@mia [Jul-04-2014-11:27:48] > After the volume is started , the information is not available in the output of the "gluster volume info" root@mia [Jul-04-2014-11:28:35] >gluster v info Volume Name: rep Type: Distributed-Replicate Volume ID: 253bf0b1-617a-496e-80f3-302904f5a9fa Status: Started Snap Volume: no Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: rhs-client11:/rhs/device0/rep_brick1 Brick2: rhs-client12:/rhs/device0/rep_brick2 Brick3: rhs-client13:/rhs/device0/rep_brick3 Brick4: rhs-client14:/rhs/device0/rep_brick4 Options Reconfigured: performance.readdir-ahead: on auto-delete: disable snap-max-soft-limit: 90 snap-max-hard-limit: 256 root@mia [Jul-04-2014-11:28:37] > Version-Release number of selected component (if applicable): =============================================================== glusterfs 3.6.0.22 built on Jun 23 2014 10:33:07 How reproducible: ================= Often Steps to Reproduce: ====================== 1. Create a dis-rep volume. 2. Check the volume info 3. Start the volume 4. Check for the volume info. Actual results: =================== Xlator 1: BD Capability 1: thin Capability 2: offload_copy Capability 3: offload_snapshot The above infomation are valid only for BD volumes. So they shouldn't be even shown for normal volumes, be it just after creation or after starting. Expected results: ======================
I see that this bug is evident with bricks of thin-p type. I tried the case where there are bricks without thin-p and I don't see capabilities listed in the 'gluster volume info' output
Closing this as a duplicate. *** This bug has been marked as a duplicate of bug 1120198 ***