iSCSI transfer is not handled gracefully, crashes network

[o7blue]

I have a network drive connected via iSCSI, so it looks like a local drive to all applications on the system (by design). I'm mentioning this since XYplorer can't tell it's a network drive either. This is what happens when I try to copy over a 40GB file (doesn't happen with files smaller than 8GB), first with explorer, then with XYplorer:

https://youtu.be/dG8nR6dupKM
(mega link to the original recording in case youtube is too blurry to make out: https://mega.nz/file/hyI00ahT#6LRg0OLGl ... TnN9RIbjdU )

So I'm not sure why the speeds drop after transferring the first 8GB (that's a separate issue unrelated to XYplorer, maybe cache filling up or something) but what matters is how explorer and XYplorer handle this. Explorer just chugs along with what looks like the max single drive speed, but XYplorer just completely locks up for 2 minutes, taking my PC's network access with it. And from when it recovers to when the transfer finishes, it's not able to match explorer's speed.

My network view: https://i.imgur.com/uIYYj8R.png

The QNAP NAS consists of all 870 EVO 4TB SSD's (in raid0), and my PC consists of 980 PRO SSD NVME's. Both are connected with CAT7 to a 10Gb switch.

Bottom line: XYplorer should be able to reduce the transfer speed without locking up itself and my PC's network access.

[TheQwerty]

It might help the developer if you share how you have custom copy configured. A screenshot of your Configuration | File Operations | File Operations | Custom Copy Operations settings and the Custom Copy | Configure... dialog will work.

I would guess that it does not occur when you have Custom Copy disabled, but you should give that a test as well. If that is indeed the case you could blacklist that path from Custom Copy using the CustomCopyBlacklist.dat file so that you can continue to use CC elsewhere until this can be addressed.

The information on how to do that is under the Configuration Dialog section of the help file or you can use this script to jump there:

Code: Select all

::help('idh_settings.htm#idh_settingscustomcopyblacklist');

[o7blue]

So I disabled CC and did a little more testing, and the results are inconsistent:

https://www.youtube.com/watch?v=2ud37xPPnNk

So far the transfer halting happens every time with XYplorer, with CC on or off. Transfer halting happens sometimes with explorer, prominently when used after XYplorer.
There is some difference in behavior but I guess the root cause lies with my NAS, not XY.

[TheQwerty]

Strange... with CC disabled it really should be the same as WE.
I'm afraid I'm out of ideas, Don will have to take a look at this when he has the time.

Sorry!

[admin]

Hmm. I guess you have to ask Microsoft. XY treats all (network) file operations the same. If CC is off the job is just given to the standard shell copy. No idea why it breaks down like this.