Comment 29 for bug 115774

This is still a problem for me on 10.04. I have a 16G root partition and my Ubuntu install takes up ~4.5G on this partition. I'm using new drivers for a TV tuner, and it sometimes causes kern.log ans syslog to fill the remaining 11G on the partition in a matter of hours. The system then becomes unstable and will not boot into X when it starts up.

Regardless of how bad my drivers might be, the kernel should not allow the root partition to fill with logs, especially when its 11G of the same two lines. This need to be fixed, but in the meantime i'm also looking for a workaround that makes the partition usable again. Right now, I'm manually running logrotate and then deleting the large files whenever this happens