[15:09] I don't understand why bcache couldn't operate on normal partitions without a superblock [15:10] It'd just need to perform writes to the partition in the same order as the filesystem itself attempted to perform them--which should be easy, since (as far as I understand) it's between the file system driver and the block device [15:11] then, if you yanked the bcache out after a power drop--even after writeback that didn't make it to the system--and mounted without bcache, you'd have exactly what would have happened in a power drop some time between the cache write and the actual power drop [15:13] You'd need a way for bcache to identify that a filesystem has changed since last mount, though, if you did that. heh. === JanC is now known as Guest13179 === JanC_ is now known as JanC === Foxtrot is now known as foxtrot