Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Thinpool block zero should be skipped while setting up LVM for RHHI. However, when backend setup is done using gdeploy, block zeroing is happening. The configuration file to test: $ cat backend.conf [hosts] 10.70.41.252 [pv] action=create devices=vdc [vg] action=create vgname=RHS_vg1 pvname=vdc [lv] action=create vgname=RHS_vg1 lvname=engine_lv lvtype=thinpool poolmetadatasize=10MB
The output should look like: [root@rhs31-c ~]# dmsetup table RHS_vg1-GLUSTER_pool: 0 104800256 thin-pool 253:2 253:3 512 0 1 skip_block_zeroing RHS_vg1-GLUSTER_pool_tdata: 0 104800256 linear 252:32 25088 RHS_vg1-GLUSTER_pool_tmeta: 0 24576 linear 252:32 104825344 rhgs_dhcp41--223-swap: 0 4194304 linear 252:2 2048 rhgs_dhcp41--223-root: 0 35643392 linear 252:2 4196352 With skip_block_zeroing for the lv created by gdeploy.
Patch posted at: https://github.com/gluster/gdeploy/pull/520
Tested with gdeploy-2.0.2-31.el7rhgs Now thinpool zeroing is skipped while creating thinpool using gdeploy conf file as mentioned in comment0 <snip> [root@ ~]# dmsetup table | grep -i zero gluster_vg_sdd-gluster_thinpool_sdd-tpool: 0 4294967296 thin-pool 253:15 253:16 2048 0 1 skip_block_zeroing </snip>
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:3830