SIGKILL failed to stop a 46 MB file copy, and the reason is buried in the Linux kernel

My computer misbehaved so I went down a rabbit hole (2019)

SIGKILL failed to stop a 46 MB file copy, and the reason is buried in the Linux kernel

A 46 MB file copy froze a whole laptop, and even SIGKILL couldn't stop it. Digging in, the author found the kernel was writing data in oversized batches, so it stayed busy and ignored signals until each chunk finished. The fix was two sysctl settings that shrink those batches, letting the system stay responsive while the copy ran in the background.

In operating systems class, we are taught that SIGKILL does not fail. We are taught that it cannot be handled, cannot be caught, cannot be ignored.

More from this day

2026-11-19