|Main Archive Page > Month Archives > clamav-users archives|
Dennis Peterson wrote:
> Marshall Dudley wrote:
>> I was running clamscan, and the var partition of the drive filled up.
>> This partition had 300 Meg free on it, and clamscan created a huge
>> number of files like mixedtextportion05GJ4k in the
>> /tmp/clamav-ec6d3e4e4e253eaf directory and filled it up. To make
>> matters worse, I had a difficult time deleting them to get the system
>> back up because when I tried to do a "rm *" it reported that the file
>> list was too long, so I had to delete them a few at a time.
> rm *[a-m];rm *[n-z];rm *[0-9]
> But an interesting problem you were left with, for sure. I sounds like a
> zip or other archive got unarchived and it was a file bomb.
OK, I know what happened then. We do maintnance on Fridays, backing up the whole system to a few zipped tars, and download them to another server across the US as well as running the clamscan. I bet that is what it was working on when it bombed. I guess I will have to split the maintance to two days so they don't conflict.