commit af247ea07a469c467b83687013a68b0e3cff05fe
Author: Alexander Gordeev <email address hidden>
Date: Thu May 5 15:52:40 2016 +0300
Add option to choose partition alignment mode
Under certain circumstances due to that alignment, the end of
particular partition could cross 1M boundary. And due to actual
partition' bounderies being rounded up, fuel-agent mistakenly
assumes that partition couldn't fit within provided boundaries
and raises errors.WrongPartitionSchemeError.
However, some h/w data storages are well known for reporting
relatively huge optimal IO sizes (16M or even bigger), so the 1M
room can't be enough. Thus, optimal aligning is not an option.
In such cases, it's better to proceed with minimal mode.
It's the minimum aligment needed to align the partition properly
to physical blocks which avoids performance degradation.
Reviewed: https:/ /review. openstack. org/312933 /git.openstack. org/cgit/ openstack/ fuel-agent/ commit/ ?id=af247ea07a4 69c467b83687013 a68b0e3cff05fe
Committed: https:/
Submitter: Jenkins
Branch: master
commit af247ea07a469c4 67b83687013a68b 0e3cff05fe
Author: Alexander Gordeev <email address hidden>
Date: Thu May 5 15:52:40 2016 +0300
Add option to choose partition alignment mode
Under certain circumstances due to that alignment, the end of WrongPartitionS chemeError.
particular partition could cross 1M boundary. And due to actual
partition' bounderies being rounded up, fuel-agent mistakenly
assumes that partition couldn't fit within provided boundaries
and raises errors.
However, some h/w data storages are well known for reporting
relatively huge optimal IO sizes (16M or even bigger), so the 1M
room can't be enough. Thus, optimal aligning is not an option.
In such cases, it's better to proceed with minimal mode.
It's the minimum aligment needed to align the partition properly
to physical blocks which avoids performance degradation.
Partial-Bug: #1543233
DocImpact
Change-Id: I1dd94731f497f3 deb47cec9a23957 e3706c2fb3b