Am 22.03.2013 15:16, schrieb Dongsu Park:
that sounds pretty much the same as what I experienced this week. After finishing some write benchmarks on a bcache device, dirty data blocks have to be synchronized to backing devices really slowly. (20~30 MB/s in my case) That sync job usually takes more than 5 minutes, which makes end users unable to do anything.
In my case, the syncing was still going on after around 16 hours (I simply let the system run after it got locked in this state). As I've only got around 2GB of page cache in the corresponding system that was used as the test bed, most probably, the system wasn't (still) flushing data, but rather spinning on something else.
The process that took most CPU time was a kworker, which migrated between CPUs. If there's any sensible way to debug this (without availability of a serial console, alas...), I'd appreciate any hints.
-- --- Heiko. -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
