On Fri, Apr 15, 2016 at 8:04 PM, Moby <moby@mobsternet.com> wrote:
On 04/15/2016 09:01 PM, Chris Murphy wrote:
On Fri, Apr 15, 2016 at 7:26 PM, Moby <moby@mobsternet.com> wrote:
Thanks to all those who replied. In the end, I take it there is no "easy" (involving something short of booting into rescue mode and changing default subvolume and then copying data over type activity) way to put the system back to an out-of-the-box state.
Uhh, I don't know how you define out of the box. It sounds like you mean reverting to the exact same subvolume tree. But it's not clear why you disqualify a rollback that involves switching to a snapshot of the subvolume tree you want. It's the same thing, in effect.
Maybe you could 'btrfs sub set-default X /" where X is the subvolume ID for the snapper ID of 1, which you'd have to find with 'btrfs sub list -t /'. I have no idea if there are consequences of switching default subvolumes outside of snapper, if it's doing its own tracking somehow.
Thanks Chris. I would define "out of the box" just as you say - basically such that if the machine were handed to someone else, they would not be able to tell that a snapper rollback was done.
Well, if they don't know where to go looking, they wouldn't know. Functionally the binaries, dates, everything, in the rollback are identical. It's just that the subvolume tree numbers are different. The extents that are references are all the same. However, there might be a work around: Btrfs seed device. The original volume set as a seed device is read-only. It's possible to mount it (read only), add a separate block device (usb stick, anything really), remount rw and now you can do all kinds of things and the changes are all COW only to the added device. You can add and delete whatever you want and on this "sprout" volume that's made up of the ro original and rw added device, those changes take effect. You can't see deleted things. But if you umount, unset seed flag setting on original and mount the original, now it's back the way it was, no changes. Of course as soon as you make changes to the original again, the sprout is busted. It can't (reliably) be used anymore. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org