Bug 1591293 - [Tracker][RFE] Support device block size of 4096 bytes (depends on RHV bug 1592916 )
Summary: [Tracker][RFE] Support device block size of 4096 bytes (depends on RHV bug 15...
Keywords:
Status: CLOSED DUPLICATE of bug 1721020
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhi-1.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1592916 1720923 1734429
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-14 13:35 UTC by John Call
Modified: 2021-09-09 14:35 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1592916 1720923 (view as bug list)
Environment:
Last Closed: 2019-06-17 07:29:22 UTC
Embargoed:


Attachments (Terms of Use)

Description John Call 2018-06-14 13:35:50 UTC
Description of problem:
RHV fails to create a Storage Domain when storage with native 4k sectors are present.  For RHHI in particular, the Gluster volume is successfully created, but RHVM reports a non-specific failure when adding the Storage Domain.  The 512-byte emulation workaround is not available with new 4kN (e.g. 4k Native) drives.


Version-Release number of selected component (if applicable):
All versions of RHV and RHHI


Additional info:
Yaniv Lavi requested this RHHI-specific bug be created.
https://bugzilla.redhat.com/show_bug.cgi?id=798947#c12
https://bugzilla.redhat.com/show_bug.cgi?id=1364869#c25

Sahina Bose shared a summary of an internal conversation on Jun 13, 2018
"I did discuss this with Yaniv Kaul and Doron F yesterday, and they mentioned they need to change the storage domain metatadata format and also cover the use cases of migrating older storage domains - hence requires a detailed design. I think this is the background for Yaniv Lavi's request - if we can focus support to RHHI specific use cases."

Comment 4 Gobinda Das 2019-06-17 07:29:22 UTC

*** This bug has been marked as a duplicate of bug 1721020 ***


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