Re: [coLinux-users] Heavy hard drive activity and lock up

[GuyBrush <guy...@gm...>]

Henry Nestler wrote:
> Am 11.02.2009 17:27, schrieb GuyBrush:
>> Hello,
>> I’m a very happy colinux user and have been using it for a while.
>> For some reason for the last two months I have been getting heavy HD
>> usage which does not allow me to run commands in the “andLinux Console
>> (FLTK)” or remote terminal.
>>
>> I’m using Andlinux which has colinux kernel ver. 2.6.22.18-co-0.7.3 and
>> I upgrade to Ubuntu 8.10. I also have the locatedb disabled in cron. I
>> tried using iotop but its not supported by the compiled colinux kernel.
>> My host OS is XP home sp3 edition.
>>
>> Is there any more information I could provide that will help give more
>> clues?
>> I tried looking at syslog and I think this part is where the system
>> stops responding with the heavy HD usage.
>> [...
>>
>> mem=256
>> root=/dev/cobd0
>> initrd=initrd.gz
>> kernel=vmlinux
>> exec0="pulseaudio\pulseaudio.exe"
>> cobd0=Drives\base.drv
>> cobd1=Drives\swap.drv
>> eth0=slirp
>> eth1=tuntap,"TAP-Colinux",00:11:22:33:44:55
>> cofs0=C:\
>>
>>
>> Is there any known problem with colinux and antivirus software on the
>> host OS?
>> I have a samba mount and I’m using Comodo Firewall, Spybot Tea Timer and
>> Avast anti virus.
>>
>> Also… I could be wrong but I notice the lockups happen when I’m not
>> watching or the computer is idling. :o)
>
> Some security software means *.drv are Windows device drivers and 
> checks the complete file before you have read/write access.
>
> Disable one of the Avast daemons to see, that is the problem you have. 
> There is something in the "expert mode" of Avast, there you can stop 
> or halt a single of the sub processes. If that is the the problem 
> exclude the coLinux image file from scanner.
>
> Rename the files "base.drv" and "swap.drv" into something that not 
> ends with "drv", for example ".img" and change the names in config 
> file. Than exclude this extension ".img" from virus scanner runtime scan.
This had worked perfectly for the past two days!
Thank you

The trick was to find the proper place to exclude files from avast scan. 
Avast has a couple of different places you can exclude files from. Right 
clicking the "a" icon near the task bar clock and clicking on program 
settings and exclusion get you to the right place.
>
> All coLinux related IO counts you can check with
> "watch cat /proc/colinux/stats"
> (only in the coLinux devel version 0.8.x)
>
> Or on the windows side you can find the task with "taskman" or the 
> tool TaskExplorer from http://www.sysinternals.com
I tried this one a little bit but It did not tell me it was avast that 
was acting up.



Thanks again and now I can go back on saving the world :o)