RE: Moving a backing device between 2 cachesets
From: Patrick Zwahlen <hidden>
Date: 2014-01-29 18:08:09
Attachments
- smime.p7s [application/pkcs7-signature] 6043 bytes
From: Patrick Zwahlen <hidden>
Date: 2014-01-29 18:08:09
-----Original Message----- From: linux-bcache-owner@vger.kernel.org [mailto:linux-bcache- owner@vger.kernel.org] On Behalf Of matthew patton Sent: mercredi 29 janvier 2014 18:51 To: linux-bcache@vger.kernel.org Subject: Re: Moving a backing device between 2 cachesetsquoted
When you register a newly formatted backing device it'll come up in passthrough mode, and then you can attach and detach a backingdevicequoted
from a cache set at runtime - while it's mounted and in use. Detaching implicitly invalidates any cached data for that backing device.so it's better to think of bcache as adding and subtracting backing (aka real devices with user data) from a notionally "static" cacheset?
That's at least how we're currently using bcache on our test setup in order to avoid using shared (SAS) SSD. I also know about interposers but never used any and would like to avoid them if possible. Moving a resource from one cachet to the other will be a rare event (maintenance, patch, test, crash) and I don't care having to start again with a cold cache in this case, including when re-assigining to resource to its original "home" cacheset. Regards, - Patrick -