On 28/01/2018 11:33 AM, Pavel Goran wrote: > Hello Coly, > > Saturday, January 27, 2018, 5:24:06 PM, you wrote: > >> Current bcache failure handling code will stop all attached bcache devices >> when the cache set is broken or disconnected. This is desired behavior for >> most of enterprise or cloud use cases, but maybe not for low end >> configuration. Nix <nix@xxxxxxxxxxxxx> points out, users may still want to >> access the bcache device after cache device failed, for example on laptops. > > In the current state, this functionality is rather user-unfriendly. > > 1. The new "stop_when_cache_set_failed" option doesn't seem to be persistent. > (At least, I did not see any explicit mechanism of saving/restoring it.) That > is, users will have to set it on each system startup. > > 2. If the new option is set to zero, it will (supposedly) lead to data > corruption/loss when cache set of a "dirty" bcache device is detached. The > option that an average home user may want to switch shouldn't be a way to > shoot oneself in the foot! > > As a remedy, the option could be changed to have the states "always" and > "auto" instead of "1" and "0", so that "auto" would still stop the bcache > device if it (or the entire cache set) is "dirty". (Alternatively, it could be > renamed to "force_stop_when_cache_set_failed" or > "always_stop_when_cache_set_failed" with values "1" and "0", if string values > are undesirable.) > > Also, the printed warning is somewhat misleading: it says "To disable this > warning message, please set /sys/block/%s/bcache/stop_when_cache_set_failed to > 1", whereas the suggested change would lead to behaviour change rather that to > just disabling the warning. > > 3. If (2) is implemented, the default value for the option could be changed to > "auto". (The rationale is that enterprise users who want it enabled are better > prepared to tune their device settings on startup.) However, this is only > important if (1) is not implemented. > Hi Pavel, I don't like "auto" since its behavior is unpredictable, sometimes whole things are gone, sometimes bcache device exists but slower, for large scale deployed environment, it is confused and misleading. After thinking for a while, I feel the "auto"/"always" options can make both enterprise and home users get an agreement. I am not able to find other better solution so far, thank you for the hint, brilliant! Personally I intend to set "always" as the default option, because I maintain bcache for enterprise workloads. The persistent option problem pointed by you does make sense, I will think how to solve it later (probably from user space tools). How do you think of this ? Coly Li [code snipped]
