Fredrik Andersson wrote:
Hi, I'd like to report what I'm fairly certain is an ext4 bug. I hope this is the right place to do so. My program creates a big file (around 30 GB) with posix_fallocate (to utilize extents), fills it with data and uses ftruncate to crop it to its final size (usually somewhere between 20 and 25 GB). The problem is that in around 5% of the cases, the program locks up completely in a syscall. The process can thus not be killed even with kill -9, and a reboot is all that will do.
does echo w > /proc/sysrq-trigger (this does sleeping processes; or use echo t for all processes) show you where the stuck threads are?
-Eric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
