Bug 1683314 - Incorrect value set for poolmetadatasize
Summary: Incorrect value set for poolmetadatasize
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.6
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1683318
Blocks: RHHI-V-1-6-Engineering-InFlight-BZs
TreeView+ depends on / blocked
 
Reported: 2019-02-26 15:08 UTC by SATHEESARAN
Modified: 2019-05-09 06:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1683318 (view as bug list)
Environment:
Last Closed: 2019-05-09 06:09:09 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1121 0 None None None 2019-05-09 06:09:18 UTC

Description SATHEESARAN 2019-02-26 15:08:51 UTC
Description of problem:
-----------------------
Thinpool poolmetadatasize is set to 3MB and its very low. As per RHGS recommendation, thinpoolmetadatasize should have value 16GB. If storage is a concern, then 0.5% of thinpool size should be set as poolmetadatasize

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
cockpit-ovirt-dashboard-0.12.3

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Start RHHI-V deployment
2. Select thinpool for bricks ( disable VDO for bricks )

Actual results:
---------------
poolmetadatasize is set to 3MB

Expected results:
------------------
poolmetadatasize should be 16GB
(or)
0.5% of thinpoolsize, if storage is a concern

Additional info:
----------------

Ideally it should be:
poolmetadatasize = minimum( 16GB, 0.5% of thinpool size )

Comment 1 SATHEESARAN 2019-03-06 07:04:54 UTC
With cockpit-ovirt-dashboard-0.12.3, the poolmetadatasize is calculated correctly with various values for brick size.
Not sure, on which occasion, we hit this problem.

Right away, closing this bug.

Comment 2 SATHEESARAN 2019-03-20 09:41:34 UTC
(In reply to SATHEESARAN from comment #1)
> With cockpit-ovirt-dashboard-0.12.3, the poolmetadatasize is calculated
> correctly with various values for brick size.
> Not sure, on which occasion, we hit this problem.
> 
> Right away, closing this bug.

Re-opening this bug as the value for poolmetadatasize lacks the UNIT and by default
lvm considers that as MB

<snip_from_inventory_file>
 - vgname: gluster_vg_sdb
          thinpoolname: gluster_thinpool_gluster_vg_sdb
          poolmetadatasize: 16
        - vgname: gluster_vg_sdb
          thinpoolname: gluster_thinpool_gluster_vg_sdb
          poolmetadatasize: 16
</snip_from_inventory_file>


<snip_from_var_log_messages>
Mar 20 14:03:09 dhcp37-83 python: ansible-lvol Invoked with pvs=None force=False vg=gluster_vg_sdb lv=None resizefs=False state=present thinpool=gluster_thinpool_gluster_vg_sdb snapshot
=None active=True shrink=False opts= --chunksize 2560K#012 --poolmetadatasize 16 --zero n size=100%FREE
</snip_from_var_log_messages>

The exact unit should be the same as thinpool size. 0.005 X ( thinpool_size ) unit

Comment 7 SATHEESARAN 2019-03-29 18:42:08 UTC
Verified with cockpit-ovirt-dashboard-0.12.6

Poolmetadatasize of thinpool is set as per requirement - 0.5% of thinpool size

Snip from the generated ansible vars file
-------------------------------------------

      gluster_infra_thinpools:
        - vgname: gluster_vg_sdc
          thinpoolname: gluster_thinpool_gluster_vg_sdc
          poolmetadatasize: 3G
      gluster_infra_lv_logicalvols:
        - vgname: gluster_vg_sdc
          thinpool: gluster_thinpool_gluster_vg_sdc
          lvname: gluster_lv_vmstore
          lvsize: 500G

Comment 9 errata-xmlrpc 2019-05-09 06:09:09 UTC
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/RHEA-2019:1121


Note You need to log in before you can comment on or make changes to this bug.