Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Is your Xubunt a 64-bit version? If so, make sure your clamscan is also 64-bit with file $(which clamscan); if not, then I don't know of any way to open files over 4GB with 32-bit software.
    – AFH
    Commented Mar 21, 2016 at 16:44
  • Thanks for the reply. "/usr/bin/clamscan: ELF 64-bit LSB executable" It's all 64-bit unfortunately. Any other ideas? Commented Mar 21, 2016 at 17:51
  • 1
    There is no way to scan arbitrarily large files, in clamav or in many other commercial AVes. There are technical difficulties (saturation of the filesystem on which /tmp resides or of virtual memory), and one very good basic reason: do you really believe that multi-GB-sized files are a good vehicle of infection? Commented Mar 21, 2016 at 17:59
  • For what it's worth, I just scanned a 13GB VM disc on 64-bit Ubuntu 15.04 and I got similar results to you; however, if I used clamscan - <FilePath it took 90 times longer, with high resource use. In both cases it reported zero data scanned, but the first call said 13GB read, while the second said 144MB. I didn't set any parameters besides the file name or -. Make what you will of these results.
    – AFH
    Commented Mar 22, 2016 at 0:35
  • 4
    If anyone has more information regarding the specific problem with scanning large files I'd like to hear it. Simply saying large "files are clean" doesn't cut it. We need to know the precise technical limitations so we can know what defaults are safe to change and under which circumstances.
    – jorfus
    Commented Dec 2, 2016 at 19:57