Bug 12649 - Can't get file status ERROR
Can't get file status ERROR
Status: RESOLVED DUPLICATE of bug 12673
Product: ClamAV
Classification: ClamAV
Component: clamscan
0.102.4
x86_64 Windows
: P3 major
: 0.101.0
Assigned To: ClamAV team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-12-21 00:24 EST by dante-skt
Modified: 2021-04-03 13:27 EDT (History)
3 users (show)

See Also:
QA Contact:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dante-skt 2020-12-21 00:24:49 EST
OS:Windows server2012 

The following message is output as a result of executing clamscan.

(File_name):Can't get file status ERROR

Commands when scanning:"C:\Program Files\ClamAV\clamscan.exe" -l (Logfile_path) -v -r --max-filesize 200M --max-scansize 200M --exclude-dir (Exclude_directory) C:\ D:\


The size of any file with an error is 2GB or more.
Therefore, it should not be scanned by [max-filesize 200M].


What is the cause of this message?
And how can I improve it?
Comment 1 Micah Snyder 2021-01-05 20:03:19 EST
Hi!

Thanks for submitting the bug report. 

It looks like this issue may be related to this bug report where clamav is scanning files larger than 2GB despite the --max-filesize setting: https://bugzilla.clamav.net/show_bug.cgi?id=12374  Can you confirm?  This issue is on my wish-list to fix for the upcoming 0.103.1 patch release, though I have a few other tasks to complete before I can investigate.

Regards,
Micah
Comment 2 dante-skt 2021-01-05 21:44:54 EST
Thank you for your answer Micah.

Confirmed case 12374.
The error message I get is different, but the fact that the max-filesize option isn't working looks the same as my report.

I hope version 0.103.1 resolves this issue.
Comment 3 Micah Snyder 2021-04-03 13:27:04 EDT
Hello!

I believe I've resolved this issue in 0.104 https://github.com/Cisco-Talos/clamav-devel/commit/861153a656bcb5266952630f0a2aaed228883404

The same fix will be included in the 0.103.2 patch release next week.

Marking this as a duplicate of ticket 12673 because it is resolved by the same patch.

Thanks for your patience.

-Micah

*** This bug has been marked as a duplicate of bug 12673 ***