+++ This bug was initially created as a clone of Bug #798947 +++ Description of problem: If you use iSCSI storage with the SATA drives in the Advanced Format is not connected to the data center storage Version-Release number of selected component (if applicable): Fedora core 16 whith Ovirt Engine, ovirt-node-image-2.2.3-1.1.fc16 in Nodes. Open-E Data Storage whith 4*2Tb Western Digital RE HDDs How reproducible: Steps to Reproduce: 1. Create iSCSI partition in open-e 2. Attach iScsi target in Datacentre 3. Error log message: Failed in vdscommand to CreateVGVDS, error = Device block size is not supported: 'logblksize=512 phyblksize=4096' Actual results: Error, iSCSI storage not connected Expected results: Connected iSCSI storage --- Additional comment from Dave Neary on 2013-03-07 12:06:39 EST --- Hi Ilya, This issue has previously been reported against Red Hat Enterprise Virtualization. It has been classified as a "request for enhancement" there - and will be prioritised as such for a future release. Thanks for your report! Dave. --- Additional comment from Itamar Heim on 2013-03-08 02:45:51 EST --- there is using 4k mode, and being able to work with them which iirc was already fixed in a later version than node you are using. ayal? --- Additional comment from Ayal Baron on 2013-03-09 15:31:14 EST --- (In reply to comment #2) > there is using 4k mode, and being able to work with them which iirc was > already fixed in a later version than node you are using. > ayal? We do not yet support using devices with a logical block size > 512B
Would you be so kind as to provide an update on this bug? My customer needed a link to our official documentation showing that we can't work with native 4k devices. I provided this link https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/planning_and_prerequisites_guide/#storage-types
(In reply to John Call from comment #19) > Would you be so kind as to provide an update on this bug? > We are looking to provide this support via Cinder, where RHV is not a part of the storage datapath.
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
What's the next step?
(In reply to Yaniv Kaul from comment #30) > What's the next step? This is dependent on Bug 1592916 targeted for 4.3.1
4.3.0 has been already released, automatically re-targeting to 4.3.3 for re-evaluation
*** This bug has been marked as a duplicate of bug 1592916 ***