[Samba] Re: Upcoming 3.0.13 release -- please test now

Dmitry Melekhov dm at belkam.com
Wed Mar 23 05:10:29 GMT 2005

Gerald (Jerry) Carter wrote:

> Hash: SHA1
> | I just upgraded two of our servers from 3.0.11 to 3.0.12
> | and found that with
> | vfs object = vscan-clamav
> | all becomes very slow and clamav eats cpu.
> | I don't know yet is this samba or vscan problem, but all were
> | OK with 3.0.11 ;-)
> My guess is a vscan issue.  If things work fine without the
> vscan module, you'll have to get their developers to debug what's
> going on.  And if they need to coordinate with us, just send
> them my email.

I just mailed to maintainer, but I'm afraid problem is in samba vfs, 
just because vscan is not more than vfs module.
I didn't read sources yet, sorry :-(

But here is vscan output with 3.0.11, when I'm writing memTest.exe to dir:

Mar 23 08:57:59 backup smbd_vscan-clamav[6247]: INFO: Scanning file : 
Mar 23 08:57:59 backup smbd_vscan-clamav[6247]: INFO: file 
/home/samba/definity/DIST/memTest.exe is clean

And here is output with 3.0.12:
Mar 23 09:00:10 chr smbd_vscan-clamav[3668]: INFO: Scanning file : 

As you see, now vscan scans _whole_  share!
Looks like there was changes in vfs code in 3.0.12 :-)

More information about the samba mailing list