Comment # 16 on bug 884111 from ill lume

I don't know how to get the kernel logs when this happens. Is there a way to
limit the amount of I/O for a program? Is there a command or bash script that
replicates the large amount of hard drive write spam so that it no longer is
able to respond to anything else?