On Tue, Dec 22, 2015 at 3:16 AM, Qu Wenruo <quwen...@cn.fujitsu.com> wrote: > Current "recovery" mount option will only try to use backup root. > However the word "recovery" is too generic and may be confusing for some > users. > > Here introduce a new and more specific mount option, "backuproot" to > replace "recovery" mount option. > "Recovery" will be kept for compatibility reason, but will be > deprecated.
I agree that this makes much more sense from a user's perspective, so +1. But why not go all the way: try backuproot automatically when the initial mount fails, log the fallback and simply deprecate/ignore the option? Either this works - in which case there is no need to involve a human, which may not even exist - or it does not. If it does not, things are hosed anyway and we can fail properly. Any reasons not to do this? -h -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
