On Fri, May 11, 2012 at 12:46:11PM -0700, Dan Williams wrote: > The consensus from LSF was that bcache need not invent a new interface > when md and dm can both do the job. As mentioned in patch 7 this series > aims to be a minimal conversion. Other refactoring items like > deprecating register_lock for mddev->reconfig_mutex are deferred. Awesome! I just applied the first 6 - the lockdep fix especially was exactly what I'd been looking for. I need to dig in to the patch that does the actual md conversion more and play with it... also need to look at how refcounting works. > This supports assembly of an already established cache array: > > mdadm -A /dev/md/bcache /dev/sd[ab] > > ...will create the /dev/md/bcache container and a subarray representing > the cache volume. "Flash-only", or backing-device only volumes were not > tested. "Create" support and hot-add/hot-remove come later. > > Note: > * When attempting to test with small loopback devices (100MB), assembly > soft locks in bcache_journal_read(). That hang went away with larger > devices, so there seems to be minimum component device size that needs > to be considered in the tooling. Curious. I normally use a 256 mb cache for vm testing and I haven't seen anything like that in ages, wonder what you found. Will investigate. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
