Closed vojtechtrefny closed 1 year ago
Patch coverage has no change and project coverage change: -0.02
:warning:
Comparison is base (
1b4b4c5
) 13.90% compared to head (b34c7f7
) 13.88%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
I decided to reuse the raid_chunk_size
argument for the LVM RAID stripe size here. I am not 100 % sure this is the best approach -- I wanted to avoid adding another LVM RAID specific argument when chunk and stripe size is basically the same thing in MD and LVM RAID, but it might be confusing. @dwlehman @richm what do you think?
I decided to reuse the
raid_chunk_size
argument for the LVM RAID stripe size here. I am not 100 % sure this is the best approach -- I wanted to avoid adding another LVM RAID specific argument when chunk and stripe size is basically the same thing in MD and LVM RAID, but it might be confusing. @dwlehman @richm what do you think?
I would prefer to have some parameter with stripe_size
in the name, but if 1) it will be difficult to add a new parameter and 2) storage admins will know that chunk_size
and stripe_size
are the same concept, then works for me. @briansmith0 wdyt?
+1 to the comment from @richm
Thank you for the feedback, I didn't realize that chunk size is also used by LVM for thin pools so using it for RAID could be confusing. #357 is replacement for this adding a new raid_stripe_size
argument.
Custom stripe size is needed for SAP HANA. We are using here the existing 'raid_chunk_size' property, the "chunk size" term comes from MD RAID where it has the same meaning as "stripe size" for LVM RAID.