Verification error when copying/moving files

[azzkiker]

Occasionally, Total Commander displays a message stating that an error has occurred during verification after a file copy or move operation. The message is: “Cannot open file!”
This error usually only occurs when Total Commander has been open for a very long time (several days) at a time. Then the error message appears reliably during almost every operation, except for small files. If Total Commander is left open for a longer period of time, the error also occurs relatively reliably with small files.
However, manually comparing the files in question immediately after the error is reported works without any problems.
After closing and reopening Total Commander, the error disappears.

I used TC v11.56 but also in previous versions this did happen sometimes.

[white]

Just to gather more info:
Did you use 32-bit TC or 64-bit TC?
Does it occur on 1 computer or more computers?
Does it occur on 1 drive or more drives?

[azzkiker]

Thanks for additional input. See my answers below:

Just to gather more info:
Did you use 32-bit TC or 64-bit TC?

I use 64-bit TC

Does it occur on 1 computer or more computers?

It did happen on 2 computers. But i do not use other computers which are running so long. My feeling is, that it happens faster on the computer with less RAM (8GB vs. 32GB)

Does it occur on 1 drive or more drives?

It is indepentend from the drive or Network connection (Windows Network Drive).

[ghisler(Author)]

You should take this very seriously: It's usually an indication of a hardware error, either bad RAM or a problem with the SSD/HDD. Try some RAM testing tools first.

[azzkiker]

Thank you for pointing that out. My current PC has been thoroughly tested for RAM errors, which is something I do with all my new computers because I've had bad experiences with this in the past. I use various endurance testing tools such as Prime95, LinpackXtreme, Y-cruncher, CoreCycler, etc. I run each program for at least 10 days in a row without restarting in between. There were no error messages.
Since this is the second computer I've had this error on, I assume it's a bug in TC that only occurs after about a week of continuous program operation using the Verify function for each copy operation.

The error never occurs within the first week or so, but after a week, the error message appears more frequently with large files (>1GB). If you let TC run even longer, the error also occurs with smaller files. If the error has occurred and you then perform a manual file comparison, no error message is ever displayed. Restarting TC fixes the problem immediately, but it reappears after about a week of regular use.
My workaround is to restart TC once every few days, then I never experience this behavior.

[ghisler(Author)]

I'm not aware of any such problem, and restarting just Total Commander should not make any difference.

If you have a lot of RAM, most of it will not be used immediately, but it will fill up more and more for the disk cache.

[azzkiker]

I typically run my system for several weeks at a time. I have not noticed any issues with other programs (e.g. WinRAR) or the test programs mentioned. All of the test programs mentioned use the entire RAM.
As an experiment, I created a RAR archive, which I have been checking in the background for days now. However, I haven't received any error messages since my last post.

The error message only appears if the verify function is activated for each copy process. Even if the error is reported, the copied file or files are always OK when checked with the comparison tool integrated in TC. I have never had a corrupt file when copying, even though I continue to use TC after the error first occurred and get the error more and more often.
The problem therefore seems to be related to the verify function, which is executed immediately after the copy process.

However, it doesn't look like a computer error to me, as I am now experiencing the same behavior with my second computer, which replaced the first one. As I already wrote, the behavior is okay for me, as I have a workaround.

[miskox]

Memory leak? Maybe you take a note of RAM used and then again after doing lots of tests. Because restart of TC solves the problem this is probably not driver related. ESET AV had a memory leak 10+ years ago - nonpaged pool got exausted.

Saso

[ghisler(Author)]

A memory leak wouldn't cause a verification error.

Is this a special disk type, e.g. a RAID (disk array)? Some RAID controllers don't work well with the direct read function which bypasses the disk cache.

[azzkiker]

Once the error has occurred (after a little more than approx. 1 week of continuous operation of TC), it occurs more and more frequently. This is independent of the source or target medium. I use SSD (SATA), SSD (NVME), HDD (SATA), and SMB shares from the NAS (not mapped with a drive letter). Only the SMB share from the NAS runs with RAID5 or RAID6. The SATA and NVME interfaces are directly from the AMD B450 chipset.

When the error occurs, files that are copied afterwards are always OK when a comparison is started manually. Only the comparison that is performed automatically immediately after the copy process causes the error. It does not matter whether the manual comparison is performed for individual files with “Compare by Content” or for an entire directory with “Synchronize Dirs”.

I use the Standard copy method but it seems copy is not the issue.

Since my last post, the error has occurred once. I then restarted TC and compared the problematic files using the TC verification function. No error was detected.

TC always requires about 25-30MB of RAM. This varies slightly depending on the current process. I have never seen TC use more than 40MB of RAM.
The free RAM is usually >10GB.