Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.`storage` system role supports configuring the stripe size for RAID LVM volumes
With this update, you can now specify a custom stripe size when creating RAID LVM devices. For better performance, use the custom stripe size for SAP HANA. The recommended stripe size for RAID LVM volumes is 64 KB.
Description of problem:
Creating LVM RAID with the Storage System Role doesn't have the option to set custom stripe sizes; it has a hard-coded default value of 64K
After a discussion with Brian Smith, this should be considered an RFE for the storage system role to support configuring the stripe size for RAID LVM volumes
Version-Release number of selected component (if applicable):
Tested on:
redhat.rhel_system_roles 1.16.2
fedora.linux_system_roles 1.30.0
How reproducible:
Running the role with specific options for an LVM RAID setup
Steps to Reproduce:
Run the following playbook:
---
- name: PoC RAID0 HANA storage with storage system role
hosts: <managed node>
become: yes
vars:
unused_disks:
- <disk1>
- <disk2>
tasks:
- name: Run storage role
vars:
storage_safe_mode: false
storage_use_partitions: true
storage_pools:
- name: hanadata_vg
type: lvm
disks: "{{ unused_disks }}"
state: present
volumes:
- name: hanadata_lv
size: 100%
mount_point: /hana/data
fs_type: xfs
raid_disks: "{{ [unused_disks[0], unused_disks[1]] }}"
raid_level: raid0
ansible.builtin.include_role:
name: fedora.linux_system_roles.storage
#name: redhat.rhel_system_roles.storage
...
Actual results:
- stripe size is set to 64K by default
[root@ansible3 ~]# lvs -ao +lv_full_name,devices,stripe_size | awk '/hanadata/'
hanadata_lv hanadata_vg rwi-aor--- 199.99g hanadata_vg/hanadata_lv hanadata_lv_rimage_0(0),hanadata_lv_rimage_1(0) 64.00k
[hanadata_lv_rimage_0] hanadata_vg iwi-aor--- <100.00g hanadata_vg/hanadata_lv_rimage_0 /dev/sdf1(0) 0
[hanadata_lv_rimage_1] hanadata_vg iwi-aor--- <100.00g hanadata_vg/hanadata_lv_rimage_1 /dev/sdg1(0) 0
[root@ansible3 ~]#
Expected results:
Similarly to raid_chunk_size, there should be the option to a custom value, if needed
Additional info:
The Azure documentation asks for specific stripe sizes here: https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-vm-operations-storage#stripe-sizes-when-using-logical-volume-managers
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 (rhel-system-roles bug fix and enhancement update), 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-2023:6946
Description of problem: Creating LVM RAID with the Storage System Role doesn't have the option to set custom stripe sizes; it has a hard-coded default value of 64K After a discussion with Brian Smith, this should be considered an RFE for the storage system role to support configuring the stripe size for RAID LVM volumes Version-Release number of selected component (if applicable): Tested on: redhat.rhel_system_roles 1.16.2 fedora.linux_system_roles 1.30.0 How reproducible: Running the role with specific options for an LVM RAID setup Steps to Reproduce: Run the following playbook: --- - name: PoC RAID0 HANA storage with storage system role hosts: <managed node> become: yes vars: unused_disks: - <disk1> - <disk2> tasks: - name: Run storage role vars: storage_safe_mode: false storage_use_partitions: true storage_pools: - name: hanadata_vg type: lvm disks: "{{ unused_disks }}" state: present volumes: - name: hanadata_lv size: 100% mount_point: /hana/data fs_type: xfs raid_disks: "{{ [unused_disks[0], unused_disks[1]] }}" raid_level: raid0 ansible.builtin.include_role: name: fedora.linux_system_roles.storage #name: redhat.rhel_system_roles.storage ... Actual results: - stripe size is set to 64K by default [root@ansible3 ~]# lvs -ao +lv_full_name,devices,stripe_size | awk '/hanadata/' hanadata_lv hanadata_vg rwi-aor--- 199.99g hanadata_vg/hanadata_lv hanadata_lv_rimage_0(0),hanadata_lv_rimage_1(0) 64.00k [hanadata_lv_rimage_0] hanadata_vg iwi-aor--- <100.00g hanadata_vg/hanadata_lv_rimage_0 /dev/sdf1(0) 0 [hanadata_lv_rimage_1] hanadata_vg iwi-aor--- <100.00g hanadata_vg/hanadata_lv_rimage_1 /dev/sdg1(0) 0 [root@ansible3 ~]# Expected results: Similarly to raid_chunk_size, there should be the option to a custom value, if needed Additional info: The Azure documentation asks for specific stripe sizes here: https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-vm-operations-storage#stripe-sizes-when-using-logical-volume-managers