<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 5, 2017 at 11:54 AM, Vinícius Ferrão <span dir="ltr"><<a href="mailto:ferrao@if.ufrj.br" target="_blank">ferrao@if.ufrj.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<br>
<div><span class="">
<blockquote type="cite">
<div>On 5 Jul 2017, at 05:35, Yaniv Kaul <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>> wrote:</div>
<br class="m_-7836893261318521319Apple-interchange-newline">
<div>
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 5, 2017 at 7:12 AM, Vinícius Ferrão <span dir="ltr">
<<a href="mailto:ferrao@if.ufrj.br" target="_blank">ferrao@if.ufrj.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Adding another question to what Matthias has said.
<div><br>
</div>
<div>I also noted that oVirt (and RHV) documentation does not mention the supported block size on iSCSI domains.</div>
<div><br>
</div>
<div>RHV: <a href="https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/administration_guide/chap-storage" target="_blank">https://access.redhat.com<wbr>/documentation/en-us/red_hat_<wbr>virtualization/4.0/html/admini<wbr>stration_guide/chap-storage</a></div>
<div>oVirt: <a href="http://www.ovirt.org/documentation/admin-guide/chap-Storage/" target="_blank">http://www.ovirt.org/do<wbr>cumentation/admin-guide/chap-<wbr>Storage/</a></div>
<div><br>
</div>
<div>I’m interested on 4K blocks over iSCSI, but this isn’t really widely supported. The question is: oVirt supports this? Or should we stay with the default 512 bytes of block size?</div>
</div>
</blockquote>
<div><br>
</div>
<div>It does not.</div>
<div>Y.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</span><div>
<div>Discovered this with the hard way, the system is able to detect it as 4K LUN, but ovirt-hosted-engine-setup gets confused:</div>
<div><br>
</div>
<div> [2] <wbr>36589cfc00000071cbf2f2ef314a62<wbr>12c 1600GiB FreeNAS iSCSI Disk<br>
status: free, paths: 4 active<br>
<br>
[3] <wbr>36589cfc00000043589992bce09176<wbr>478 200GiB FreeNAS iSCSI Disk<br>
status: free, paths: 4 active<br>
<br>
[4] <wbr>36589cfc000000992f7abf38c11295<wbr>bb6 400GiB FreeNAS iSCSI Disk<br>
status: free, paths: 4 active</div>
<div><br>
</div>
<div>[2] is 4k</div>
<div>[3] is 512bytes</div>
<div>[4] is 1k (just to prove the point)</div>
<div><br>
</div>
<div>On the system it’s appears to be OK:</div>
<div><br>
</div>
<div>Disk /dev/mapper/<wbr>36589cfc00000071cbf2f2ef314a62<wbr>12c: 214.7 GB, 214748364800 bytes, 52428800 sectors<br>
Units = sectors of 1 * 4096 = 4096 bytes<br>
Sector size (logical/physical): 4096 bytes / 16384 bytes<br>
I/O size (minimum/optimal): 16384 bytes / 1048576 bytes<br>
<br>
<br>
Disk /dev/mapper/<wbr>36589cfc00000043589992bce09176<wbr>478: 214.7 GB, 214748364800 bytes, 419430400 sectors<br>
Units = sectors of 1 * 512 = 512 bytes<br>
Sector size (logical/physical): 512 bytes / 16384 bytes<br>
I/O size (minimum/optimal): 16384 bytes / 1048576 bytes</div>
<div><br>
</div>
<div>But whatever, just reporting back to the list. It’s a good ideia to have a note about it on the documentation.</div></div></div></div></blockquote><div><br></div><div>Indeed.</div><div>Can you file a bug or send a patch to upstream docs?</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>V.</div>
</font></span></div><div><div class="h5">
<br>
<blockquote type="cite">
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div><br>
</div>
<div>Thanks,</div>
<div>V.</div>
<span>
<div><br>
<div>
<blockquote type="cite">
<div>On 4 Jul 2017, at 09:10, Matthias Leopold <<a href="mailto:matthias.leopold@meduniwien.ac.at" target="_blank">matthias.leopold@meduniwien.a<wbr>c.at</a>> wrote:</div>
<br class="m_-7836893261318521319m_7491295833897249589Apple-interchange-newline">
<div>
<div><br>
<br>
Am 2017-07-04 um 10:01 schrieb Simone Tiraboschi:<br>
<blockquote type="cite">On Tue, Jul 4, 2017 at 5:50 AM, Vinícius Ferrão <<a href="mailto:ferrao@if.ufrj.br" target="_blank">ferrao@if.ufrj.br</a> <<a href="mailto:ferrao@if.ufrj.br" target="_blank">mailto:ferrao@if.ufrj.br</a>>> wrote:<br>
Thanks, Konstantin.<br>
Just to be clear enough: the first deployment would be made on<br>
classic eth interfaces and later after the deployment of Hosted<br>
Engine I can convert the "ovirtmgmt" network to a LACP Bond, right?<br>
Another question: what about iSCSI Multipath on Self Hosted Engine?<br>
I've looked through the net and only found this issue:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1193961" target="_blank">https://bugzilla.redhat.com<wbr>/show_bug.cgi?id=1193961</a><br>
<<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1193961" target="_blank">https://bugzilla.redhat.co<wbr>m/show_bug.cgi?id=1193961</a>><br>
Appears to be unsupported as today, but there's an workaround on the<br>
comments. It's safe to deploy this way? Should I use NFS instead?<br>
It's probably not the most tested path but once you have an engine you should be able to create an iSCSI bond on your hosts from the engine.<br>
Network configuration is persisted across host reboots and so the iSCSI bond configuration.<br>
A different story is instead having ovirt-ha-agent connecting multiple IQNs or multiple targets over your SAN. This is currently not supported for the hosted-engine storage domain.<br>
See:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1149579" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1149579</a><br>
</blockquote>
<br>
Hi Simone,<br>
<br>
i think my post to this list titled "iSCSI multipathing setup troubles" just recently is about the exact same problem, except i'm not talking about the hosted-engine storage domain. i would like to configure _any_ iSCSI storage domain the way you describe it
in <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1149579#c1" target="_blank">
https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1149579#c1</a>. i would like to do so using the oVirt "iSCSI Multipathing" GUI after everything else is setup. i can't find a way to do this. is this now possible? i think the iSCSI Multipathing documentation
could be improved by describing an example IP setup for this.<br>
<br>
thanks a lot<br>
matthias<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</span></div>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div></div></div>
<br>
</div>
</blockquote></div><br></div></div>