Hi,
I am running clamscan on imx6q sabresd board which has 1GB of RAM. A few months back, I got an OOM killer while running clamscan which killed the clamscan process. So, as a workaround, I introduced a swap of 2GB which worked and fixed the OOM killer issue.
But, now if I create a swap file of 2GB and run clamscan, the board reboots sometimes, and sometimes the scan is successful. RAM usage is quite high and at times only 5MB of it is left free while running clamscan and swap usage goes as high as 500MB.
The difference between the above two cases is the introduction of approximately 80,000 new virus signatures. I am quoting this comment here https://unix.stackexchange.com/a/278110, "The problem is the huge number of virus signatures. This leads to the algorithms' datastructures growing quite large. You can't send those datastructures to swap, as there are no parts of the algorithms' datastructures accessed less often than other parts."
My concern is the random rebooting of the board. Why running clamscan is rebooting the board? Why swap file is no more effective? I mean, Introducing a swap file could cause performance degradation, but a reboot shouldn't occur in any case!
So, here are my questions:
Is clamscan supposed to work by introducing swap in low-memory systems?
What might be causing the board to reboot in this case and how it can be fixed?
Any help would be appreciated!
Thanks,
Tariq?
I am running clamscan on imx6q sabresd board which has 1GB of RAM. A few months back, I got an OOM killer while running clamscan which killed the clamscan process. So, as a workaround, I introduced a swap of 2GB which worked and fixed the OOM killer issue.
But, now if I create a swap file of 2GB and run clamscan, the board reboots sometimes, and sometimes the scan is successful. RAM usage is quite high and at times only 5MB of it is left free while running clamscan and swap usage goes as high as 500MB.
The difference between the above two cases is the introduction of approximately 80,000 new virus signatures. I am quoting this comment here https://unix.stackexchange.com/a/278110, "The problem is the huge number of virus signatures. This leads to the algorithms' datastructures growing quite large. You can't send those datastructures to swap, as there are no parts of the algorithms' datastructures accessed less often than other parts."
My concern is the random rebooting of the board. Why running clamscan is rebooting the board? Why swap file is no more effective? I mean, Introducing a swap file could cause performance degradation, but a reboot shouldn't occur in any case!
So, here are my questions:
Is clamscan supposed to work by introducing swap in low-memory systems?
What might be causing the board to reboot in this case and how it can be fixed?
Any help would be appreciated!
Thanks,
Tariq?