Hello Nik, Wednesday, June 11, 2014, 9:48:20 PM, you wrote: > I have been running bcache in writeback mode for a while, and had an > unclean shutdown due to a power outage. Machine rebooted, did an > fsck, everything seemed ok, I had a few corrupt files that were open > when the shutdown happened, but no major deal. Then, I started > getting hung tasks: > INFO: task bcache_writebac:1582 blocked for more than 120 seconds. This looks like a well-known bug that manifests itself with the "bcache_writeback locked" messages. It's possible that your cache was corrupted and disabled because of this, and now the bcache_writeback task has no work to do and because of this the "locked" messages appear. (Personally I get these messages when using a bcache device without cache.) Bottom line: these messages probably appear because bcache is *already* disabled. > How can I disable bcache for now? The instructions to install it a > pretty clear, but disabling it isn't. Check whether cache is currently active: cat /sys/block/bcache0/bcache/state If it says "no cache", then there is no active cache on the bcache0 device. If it says "clean", then the cache is there. To disable bcache for the device bcache0 you need to issue the following command: echo "4faa930e-1983-45d3-ac40-e7dd0941d63c" | tee /sys/block/bcache0/bcache/detach Substitute "4faa930e-1983-45d3-ac40-e7dd0941d63c" with the ID of your cache (you can find cache IDs by looking at the /sys/fs/bcache directory). Pavel Goran -- 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
