On Fri, Apr 25, 2014 at 11:35 AM, SR <srju...@gmail.com> wrote: > 2014-04-25 10:58 GMT-04:00 Shawn Webb <sw...@sourcefire.com>: > > Hey Stephen, > > > > How big is that file? How much RAM (physical and swap separate, please) > is > > installed on the scanning machine? Currently, ClamAV has a hard file > limit > > of around 2.17GB. Because we're mapping the file into memory, if you > don't > > have enough memory available to map the whole file, the memory mapping > code > > (as currently implemented) will fail and the file won't be scanned. > > > > One of our long-term goals is to investigate being able to properly > support > > large files. > > > > Thanks, > > > > Shawn > > _______________________________________________ > > > Hi Shawn, thanks for your quick reply. > > The file I referred to in my previous message is 936MB. I have other > large files but smaller than 2GB. > > The server is running on a VM (ESX-i) with 1GB ram allocated to it. > I will try doubling the RAM for a test, but I find reserving 2GB for a > home file server VM is a bit overkill. > > My concern is that since a recent update, the behaviour of clamDscan > seems to have changed. > In my opinion, files this big should be ignored and not loaded. > > Finally, I don't know if it is a direct relation; but I have found the > following > which seems be related to the fmap() memory allocation problem (at least > on a > Debian distribution) > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740059
The full signature set for ClamAV (main + daily + bytecode) takes up a good chunk of memory as well (around 350MB on my FreeBSD/amd64 box). Having the full signature set loaded and trying to scan a 936MB file will surely make ClamAV attempt to use more than 1GB memory. Either adding swap space (which will cause ClamAV to work--albeit very slowly) or assigning more memory to this VM is your solution here. I'll have a talk with the team at a later date regarding possible solutions we can implement on our side. Thanks, Shawn _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/support/ml
