Insufficient System Resources

[Mwyarm]

I am copying several large files from my HDD drive to an external HDD drive. In recent copies of 3GB files or larger the copy process gets to a point where it states "cannot copy file" and shows on the destination drive a "xxx.ffs_tmp." It appears FFS writes data to a "tmp" file which is fine but pops the Insufficient System Resources message when it appears the external HDD drive is still writing the data. It is almost like FFS is waiting for confirmation a write is complete and because the write has not happened it throws up the message like it "timed out" waiting for the write. Obviously, the external HDD drives are much slower in writing. Or possibly however or whatever it writes to the "ffs.tmp" file is too large for the file to be written. I notice teh "ffs.tmp" size differs each time I press "retry." I am not sure how that file is built but between the "tmp" file and HDD still writing there is a disconnect on more time is needed, I believe.

I have over 64GB of memory as it is a new PC and I loaded up on memory to avoid issues like this and during the task only about 8% of memory is being used. There is over 100GB of storage remaining on the external drive so that is not the issue.

So when the message pops up, I click retry and it starts again but I can tell each time it is getting further and further in what it has written as the start point is different.

Is there a fixed "time out" parameter before FFS declares a "cannot copy file" message when it is simply impatient waiting on the write? I really don't know so I am guessing based on how I see the PC operating at 1GB card and knowing the HDD cannot write that fast. I don't see the problem on smaller file sizes.

Also, so, after 3 or 4 attempts retrying I eventually give up and press "ignore" or "ignore all" but that creates problems as such. Since it has now skipped the file, FSS indicates the synchronization is complete and displays the files I skipped. I click on "Synchronize" and I get "waiting while directory is in use "J:\sync.ffs_lock." So, FSS locked the directory but somehow doesn't know to release the lock to restart the synchronization again after you have ignored files. The external HDD drive is not writing anything since the prior synchronization is finished so it is not waiting o the external HDD drive. I can wait 10 minutes or 2 hours and it is still "waiting." I close FSS, I close all related open windows, and I check task manager and nothing appears to be the culprit on why it is waiting. I search in the directory for "ffs_lock" and I checked both hidden and normal and there is no such file? The only way around it is to reboot the PC to clear off whatever is held up. So, after the reboot, I have to go back and do a scan again on what is different to find the file that I could not copy previously. I read there is a parameter where you can have FSS to ignore locks but I like that feature. I just want FSS to know it locked the files on the first synch and when I skip files and it completes synchronization it needs to release the lock.

Any help would be appreciated.

[therube]

external HDD drive

Tell us about the drive? How is it formatted?

3GB files or larger

If FAT32, FAT32 is limited to file sizes < 4GB (so a 3GB file should work).

In recent copies

So does that imply that the same sized files did copy successfully in the past?

Insufficient System Resources

Can mean many things.
To me, it would make want to check for something like a Handle leak.
What OS are you running?

[Mwyarm]

External drive file system is NTFS. I have used FFS for 3-4 years now and I appreciate the product and I have made donations. I don't recall this issue previously so something has changed. Certainly a much newer PC with a new gaming type motherboard, 1gb cards, and 64GB of memory so the PC if any anything is overdone to most PC standards.

I have
OS Name Microsoft Windows 10 Pro
Version 10.0.19043 Build 19043
System Manufacturer ASUS
System Type x64-based PC
Processor AMD Ryzen 9 3900X 12-Core Processor, 4000 Mhz, 12 Core(s), 24 Logical Processor(s)
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product ROG CROSSHAIR VIII HERO (WI-FI)
Installed Physical Memory (RAM) 64.0 GB
Total Physical Memory 63.9 GB
Available Physical Memory 54.3 GB
Total Virtual Memory 73.4 GB
Page File Space 9.50 GB

I noticed in the Synchronization window it shows how fast it is reading, or is writing, but when it gets to the point where I see the PC is no longer reading or writing, the FSS synchronization window shows the speed going from 73MB to 0MB and sits there for a long time. That makes sense as the external HDD is still writing based on the light and sound of the drive spinning. The window stays at 0MB while it is waiting for the external HDD drive to finish.

Something of interest occurred last night. As I shared above, I had to reboot my PC to synch the 3.2GB file after I pressed ignore and I cannot ever get past the "waiting for lock file message." It is frustrating that FSS locks something on it its initial synchronization and it does not release it after I press ignore file and it completes the synchronization. After my reboot the 3GB file is the only file to synch and FSS shows in its window that is ramps up to 100MB and then settles in somewhere between 70MB - 50MB and then after a minute or so it goes to 0MB. The HDD is still writing at a high speed. With only 1 3GB file it did the above as I described but the external HDD finished writing and FSS said successfully complete. It works when there is 1 file but not when large files are among many others sometimes. I say that as I saw another larger file but slightly smaller and it wrote it without the error message (possibly under 3GB - don't know).

I don't know the inter workings of FSS but hopefully someone that understands what it does when reading and passing the data to write could help determine where to go especially since a reboot with the single file works?

I will have to pay closer attention to the file sizes but it is never on any small size file (up to 2.5GB has never shown that message so something along the 3GB limit appears to be the breakpoint depending on what it is doing with other files???
Thanks for your help.

[xCSxXenon]

That's so odd...
Try doing a test sync to a different location, not to that external drive. That way we can tell if the issue is on the source side, or the destination. Maybe that external drive is starting to fail? If it is obviously doing something but FFS says 0MB/s, what is it doing? Run something like gsmartcontrol, double click the external drive, go to the attributes tab, and attach a screenshot of that. Look for RAW READ ERRORS, UNCORRECTABLE, REALLOCATIONS, PENDING UNCORRECTABLE, etc.

[therube]

Perhaps, Stuck lock files?

[gnome_mo]

I have the same issue. Backuping 1Tb of different work files to a (new) NAS.
Had about 50-70 of (ignored) errors, all of the files were PDFs containing CAD drawings (don't know if that matters).
Do I have to say, it took forever to finish syncing, because it hangs on every error, even though I pressed "ignore all"?

Original error message:

Error Cannot move file
"Z:\Sync from desktop\Folder\Name of the file~5c6a.ffs_tmp" to
"Z:\Sync from desktop\Folder\Name of the file.pdf".
ERROR_NO_SYSTEM_RESOURCES: Insufficient system resources exist to complete the requested service. [MoveFileEx]


*PC has enough resources, CPU has 16C/32T, 128 Gb RAM...it's an overkill for most purposes.

[therube]

OS?
Tell us about your NAS?
About how many files are you dealing with?

"Resources" can mean more then simply "CPU" & "RAM".

If MoveFileEx "resources" are the same as (& they might not be) "[WinError 1450] Insufficient system resources exist to complete the requested service" (along with, "when you leave your computer on for a long time, when you plug into a USB drive, or when you're trying to launch some .exe files like the Chrome browser, iTunes, Microsoft Edge, etc. Then the computer will get freezing or stuttering. After a PC reboot, the error may happen again and stop your computing"), then the suggestion there, dealing with "LanmanServer" - certainly made me laugh (as I mentioned "LanmanServer" back in 2005 [& WinXP at the time]).

(And if Win10 has this issue, you can be sure it is there too in Win11, lol.)


2005, Not enough server storage to process command?

[gnome_mo]

Win 10
Western Digital My Cloud Home 4Tb
None of the scenarios you mentioned.
Recently rebooted PC, started sync and went about my business, 4 h later we have this:
https://imgur.com/06Ha9YP
As you can see, it hangs an hour already on one file, .pdf
Transfer rate: 0 bytes/sec

[xCSxXenon]

Is it the same file every time?

[Mwyarm]

For my original issue I ran a memory check and it determined 1 of the 4 memory sticks was bad. And for the issues where it would just "sit" processing the file I found some to be 'left over" FFS locks on the file. I cannot recall if I have seen that since replacing the memory stick but I always go out to the folder and look for any instances of FFS locks and delete those. They should not be there but for some reason on some occasions they get left over and hoses the next execution. Something to investigate.

[gnome_mo]

Is it the same file every time?

No, I have heaps of the same error. Interestingly enough, they're all pdf files.
Mwyarm, I don't know what ffs lock is? I'm new at this.

[Mwyarm]

In the default configuration when you select 2 folders to compare it creates a file titled "sync.ffs_lock" to avoid another user from attempting to update the folder(s) when the synch is running. Test it for yourself by taking 2 folders and after you click compare go to the folder you selected and you should see the above file name. When the compare is complete that file should go away as it is only intended to be present during an FFS execution. If it is present delete it as it will create at the next compare. It is just a suggestion. There are far more people that know more than me but if a synch compare was abruptly ended somehow possibly there is still some lock? Do run a memory test just to be sure also just to clear no resource issues.