Sorry !
Le jeu. 26 oct. 2017 à 14:55, Dan Streetman a
écrit :
> Mathieu,
>
> I'm not mailing you, this is a public bug report, you subscribed
> yourself to this bug:
>
> 2017-01-26 10:14:29 Mathieu Perona bug added
> subscriber Mathieu Perona
>
> --
> You received this b
Dear Dan,
I am not sure you are mailing the right person. Anyway, the issue still
arises when copying large files from a FAT drive to an EXT one. kswapd uses
all available CPU power (but leaves much of the RAM unused) and copy
throughput declines.
Anyway, I solved the problem by transferring my e
Did you try this from Rasmussen up above?
sudo touch /etc/udev/rules.d/40-vm-hotadd.rules
reboot
That fixed it for me on EC2
On Saturday, 3 September 2016, Andy Robertson
wrote:
> All of my t2.micro & nano instances are affected by this in AWS EC2
> after upgrading to Ubuntu16.
>
> doing "echo
Thank you so much Rasmus!
Your solution worked for me:
sudo touch /etc/udev/rules.d/40-vm-hotadd.rules
reboot
I could always trigger the CPU usage bug with this:
stress --cpu 8 --io 4 --vm 7 --vm-bytes 128M --vm-hang 3 --timeout 60s
If running it once didn't work, a second run would do it. Now I
I've had the issue mostly when running with no swap. I added 1GB swap
file and it fixed it on the machine with less memory usage, but the
machine with the database (using more memory most of the time) still has
the bug occur about once a day.
Ubuntu 16.04 for both, not happening on 14.04.
Sent fr
