On Sun, Sep 15, 2013 at 07:34:46PM +0200, Rolf Fokkens wrote: > When no caching devices are connected, bcache-status shows nothing. > Although actually no caching happens, it's confusing. Aha, I didn't quite understand what you were getting at until I broke one of my cachesets. Yes, it would be useful to have it report orphaned cache / backing devices, since right now it only prints full sets in /sys/fs/bcache/$uuid/. --D > > On 09/15/2013 06:54 PM, Rolf Fokkens wrote: > >Yep, works indeed. > > > >Dispite the alarming description :-) > > > >Suggestion for alternative text: "Detaches all caching devices > >and closes them; if any data is present in the caching devices it > >will ..." > > > >On 09/15/2013 05:42 PM, Rolf Fokkens wrote: > >>On 09/15/2013 05:20 PM, Gabriel de Perthuis wrote: > >>>Cache sets have an 'unregister' action: > >>>/sys/fs/bcache/<uuid>/unregister The reference docs are in > >>>bcache.txt. http://atlas.evilpiepirate.org/git/linux-bcache.git/tree/Documentation/bcache.txt?h=bcache-dev#n367 > >> > >> > >>I noteced that one, but it looks kind of scary to me: > >>|"Detaches all backing devices and closes the cache devices; if > >>dirty data is present it will disable writeback caching and wait > >>for it to be flushed.| > >>Sounds like one of these: > >>- the /dev/cache* devices are gone; if so: that's definitely not > >>what I want. > >>- or at least the the baching devices are detached; that also > >>sounds bad. I don't want to detacht the backing devices at all, > >>I want to detacht the caching device. > >> > >>The text is somewhat confusing to me. I'll give it a try, it's > >>only a VM. > > > -- 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
