For the backing device, I think things will just work - you'll just have to close and reopen the backing device in order for bcache to notice the new size. Bcache's superblock doesn't remember the size, it just goes off of what the size of the backing device is when it's registered. There's currently no way to make bcache notice the backing device has grown to do it at runtime, though that ought to be fairly simple too. On Wed, Apr 11, 2012 at 6:47 PM, David Rhodes Clymer <david@xxxxxxxxxxxxxx> wrote: > In the case where the bcache backing store is resizeable (eg. a > logical volume), is it possible to resize the backing store without > breaking bcache? Let's say, for example, that I would > unmount/unregister /dev/bcacheX, resize the backing store, > reregister/remount the cache. > > I imagine a better approach would be to layer LVM on the cache device > itself. However, in this particular case, I set up the bcache before I > had learned how to get LVM to use a bcache device as a PV. > > -davidc > -- > 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 -- 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
