clamav-users October 2011 archive
Main Archive Page > Month Archives  > clamav-users archives
clamav-users: Re: [clamav-users] Value too large for defined dat

Re: [clamav-users] Value too large for defined data type

From: Török Edwin <edwin_at_nospam>
Date: Fri Oct 14 2011 - 09:02:22 GMT
To: clamav-users@lists.clamav.net

On 10/14/2011 11:49 AM, Simon Friedberger wrote:
> Hello everybody,
>
> I'm getting the following error trying to scan a file:
>
> WARNING: myfilename: Can't access file
> myfilename: Value too large for defined data type

This probably comes from the stat() system call.
It can happen if you use an XFS with inode64 option and 32-bit apps for example, and it'll happen with any 32-bit app (try gcc).

>
> It seems that this error can be caused by different problems like a wrong inode number when mounting CIFS or very large files. (Suggested by some websites and old mailing list entries.)

What is your filesystem? What is your kernel ('uname -mrsp')?
Are you running a 32-bit or 64-bit ClamAV? ('file /usr/bin/clamscan' will tell you)

>
> I have three questions:
>
> 1. How do I find out which value really causes the issue?

Does 'stat myfilename' work?

> 2. How do I scan very large files?

I don't think its the file's size the problem, but rather its inode.
Use a 64-bit clamscan/clamd if your filesystem uses 64-bit inodes.

> 3. How do I find out what the current maximum file size for scanning is? The man page says the default is 25 MB but it is not set in /etc/clamav/ anywhere and I have scanned files larger than that.

If you scan something outside the limits you don't get an error, you get an OK.

Best regards,
--Edwin
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml