How to determine which files have access errors

My backup includes a very large number of files in a large number of dirs. At the end of an operation, I am seeing:

18 files were not included due to access errors

I have attempted to redirect stderr to a separate file, but it keep coming up empty. There are no obvious occurrences of any sort of an ERROR style message in the stdout output I have captured via tee.

What is the best way to identify (on Linux) the culprits please?

2 Likes

If you go back in the log file you’ll find that there is a log message for each file that can’t be opened.

But it’s difficult to search through the whole log for that.
I think a good feature would be that the error log should be also listed at the end of the backup. After (or before?) the “all these files were backed up this run”.

Should i make a feature request for this?

Is there any particular pattern I can search for to locate these? I have captured all stdout and stderr but am not seeing anything obvious such as ERROR (or something similar) to indicate this?