cgrenier wrote:If you run "photorec_win.exe /log", a log file name photorec.log will be created. It will record the name of the file that failed to be created.
Oh my! I had already looked at the log-file (I ran photorec with /debug /log) but I was looking at the end of it thinking it was a true log-file while instead it's a report-like file. This is the error but apparently it doesn't have anything to do with file names (though it's not the only disk image I had issues with):
Code: Select all
Cannot create file /recovery1/recup_dir.154/f7263734.txt: Too many open files
PhotoRec has been stopped
Can't create photorec.ses file: Too many open files
I used Nirsoft "OpenedFilesView" to view which files were left open but there were all kinds of them (zip, doc, xls, exe, etc.). There are at least a couple open files in most of the recup_dir folders. Could it be that those are files left open waiting to be completed by the brute-force option?