Unable to use FileIO for large amounts of content about unraid.iscsi HOT 6 OPEN

Latest versions are used at build time and are specific to the kernal for the unraid release.

from unraid.iscsi.

targetcli is as of March 2021. Which Unraid vers are you running

from unraid.iscsi.

@Dids can you please be a little bit more specific?
What kind of filesystem did you use, what file and what filesize did you try to copy over?

from unraid.iscsi.

@Dids please give us more details, otherwise the issue will be closed.

from unraid.iscsi.

@ich777 I will try to reproduce this today using the latest version of the plugin and get back to you with more details.

from unraid.iscsi.

So I was able to reproduce this again, and it may simply be a limitation of FileIO, or simply against its use case scenarios.

In my specific case, I was attempting to install Windows 10 on it, which I know is not adviced even if just for the speed impact of using FileIO vs block storage devices, and while installing, the following is repeated in syslog:

kernel: Unable to recover from DataOut timeout while in ERL=0, closing iSCSI connection for I_T Nexus iqn.2021-06.foo:bar,i,0x400001370000,iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.f75143e7efd8,t,0x01

The installation seems to finish however, and from what I could gather this is simply a warning that the client is writing too much data and it will retry writing later, so shouldn't break anything, I'm assuming?

After the installation has finished (and I've disabled pagefile in the registry, as otherwise it would BSOD from that), whenever I try booting Windows 10 from iSCSI target, the following is repeated in syslog:

kernel: FILEIO: Not able to process I/O of 10841088 bytes due toFD_MAX_BYTES: 8388608 iovec count limitation

While I was under the impression that this is also harmless, it seems to produce various BSODs and I've yet to get past those. In most cases it's reporting missing files, such as BCD and ntoskrnl.exe, which tells me that even the bootloader is unable to properly load itself/all the files it needs.

My best guess is that this is simply something that FileIO cannot do/handle, which is fine, I just wanted to be sure and to know if there are known issues or workarounds for this use case.

Either way, using a block storage device works perfectly fine, so this is not a blocking issue in any way, simply something possibly worth noting about FileIO, if it is indeed not capable of handling a large I/O load such as an entire OS.

Feel free to close this issue whenever, but I would appreciate your thoughts on this regardless, and I'd be happy to provide any more information you might need. :)

from unraid.iscsi.