On Sun, Jul 27, 2014 at 10:53:04PM -0400, Austin S Hemmelgarn wrote: > >>> But, for right now I'd prefer the admin get involved in using the backup > >>> supers. I think silently using the backups is going to lead to > >>> surprises. > >> Maybe there could be a mount non-default mount-option to use backup > >> superblocks iff the first one is corrupted, and then log a warning > >> whenever this actually happens? Not handling stuff like this > >> automatically really hurts HA use cases. > >> > >> > > This seems better and comments also shows this idea. > > What about merging the behavior into 'recovery' mount option or adding a > > new mount option? > Personally, I'd add a new mount option, but make recovery imply that option.
I agree with that, though we do not need introduce an extra option if the meaning is denendent on 'recovery', but rather make it a mode of recovery (and we could add more in the future). Eg. $ mount -o recovery=sb which would try to use all valid backup superblocks to mount. -- 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
