Bug 1729809 - [RFE] Support 4k storage - imageio
Summary: [RFE] Support 4k storage - imageio
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-imageio
Classification: oVirt
Component: Common
Version: 1.5.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.3.8
: 1.5.2
Assignee: Nir Soffer
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1592916 1734429
TreeView+ depends on / blocked
 
Reported: 2019-07-15 00:26 UTC by Nir Soffer
Modified: 2020-02-26 16:32 UTC (History)
7 users (show)

Fixed In Version: ovirt-imageio-1.5.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-26 16:32:12 UTC
oVirt Team: Storage
Embargoed:
sbonazzo: ovirt-4.3?
sbonazzo: ovirt-4.4?
sbonazzo: planning_ack?
sbonazzo: devel_ack?
sbonazzo: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 101788 0 'None' MERGED ioutil: Add blksszget() 2020-04-30 09:21:26 UTC
oVirt gerrit 101904 0 'None' MERGED docs: Rewrite development.md 2020-04-30 09:21:33 UTC
oVirt gerrit 101905 0 'None' MERGED build: Add userstorage for tests 2020-04-30 09:21:29 UTC

Description Nir Soffer 2019-07-15 00:26:11 UTC 
Description of problem:

ovirt-imageio assumes block size of 512 bytes, uploading and downloading images
to/from storage using 4k block size will fail.

Need to detect the block size of underlying storage and use it instead of the
hard-coded value.
Comment 1 Nir Soffer 2019-07-15 15:44:44 UTC 
We need this for 4k on RHHI, so 4.3.6.
Comment 2 Nir Soffer 2019-08-20 16:04:21 UTC 
ovirt-imageio 1.5.2 includes this change.
Comment 6 SATHEESARAN 2020-01-28 08:00:19 UTC 
Tested with RHV 4.3.8 + RHGS 3.5.1 ( glusterfs-6.0-29.el7rhgs )

1. All the RHHI-V core cases are run with 4K disks as well as with 4K VDO devices.
2. Deployment and functionally works good without any issues
Comment 7 Sandro Bonazzola 2020-02-26 16:32:12 UTC 
This bugzilla is included in oVirt 4.3.8 release, published on January 27th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.3.8 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.