On Fri, Dec 5, 2014 at 11:27 AM, James West <ja...@terminalsystems.com> wrote:
> General idea would be to have a transient snapshot (optional quota support > possibility here) on top of a base snapshot (possibly readonly). On system > start/restart (whether clean or dirty), the transient snapshot would be > flushed, and the system would restart the snapshot, basically restarting > from the base snapshot. Sounds similar to this idea: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html About 1/3 of the way down it gets to a proposal to Btrfs as a way to get to a stateless system, which is basically what you want to be able to rollback to. A variation on this that might serve the use case better is seed device. You can either drop the added device that stores changes to the seed device, or the volume (seed+added device) can become another seed if you want to make the current state persistent at next boot. And still another possibility is overlayfs, which isn't Btrfs specific. -- Chris Murphy -- 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
