Multi Commander > Support and Feedback

[BUG] Moved file has size 0

<< < (3/3)

edge91:
I tried disabling my AV and firewall, still the same results. There's no antivirus or firewall on the NAS.

I'll try from another computer tomorrow.

Mathias (Author):
Found this in user comments on Amazon for that NAS D-Link 320
http://www.amazon.com/D-Link-DNS-320-ShareCenter-Network-Enclosure/dp/B004SUO450   (comment from April 6, 2012)


--- Quote ---"Since the November 2011 release of Firmware 2.02, users have been reporting data integrity problems with the box - including files that get copied and then show up as "0 bytes". (See forums.dlink.com for DNS-320)"
--- End quote ---

So it might be a NAS issue. you can try to turn off optimized file copy in MC, then file copy will be less optimized but it might be what the NAS needs.
Either disable "Automatically detect read/write strategy for file copy" then the unoptimized read/write will always be done.
or you can tweak just that read/write strategy used for your network copy.. I guess to will be "To Network" (if it detects it correct) and then enable all checkboxes for write options.

edge91:
To network --> Write options(Target) --> Use system cache should be checked, then it works like a charm.

Maybe this could be the default settings in future releases?

BTW. thank you for pointing that bug for the NAS, I really didn't have a clue that other people were experiencing problems... I know I've never had problems with it so I assumed it isn't the problem... I will have to check for new firmware.

Mathias (Author):

--- Quote from: edge91 on February 26, 2014, 23:29:20 ---To network --> Write options(Target) --> Use system cache should be checked, then it works like a charm.

Maybe this could be the default settings in future releases?

--- End quote ---

No. MC has to assume that hardware works as they should, and how Windows require the hardware to work.

Enabling System Cache will hurt performance a bit since all data that should be written will now also be cached by Windows.
It can also give you false sense of the progress, since the progress you see is when the data have been sent to the cache, not the actual drive/target device.
And it can also give you a jerky copy experience, First the progress goes very fast, then it stops/halt because the system cache is full and everything stop and wait until all the data have actually been written and then it continues. And it continues to do so. This is specially seen on large files. But also depends on how much RAM you got left that the system uses for cache.

Navigation

[0] Message Index

[*] Previous page