> atime). Also, this might break some configurations not expecting the > set-default method
I have never seen this before. Can you extend on this or provide a link so i can read more about such limitation? > > > 2. reboot > > b) always mount into snapshot > > 1. mount -o suvol=/.current $disk # at initrd > > 2. btrfs subvol del /.current > > 3. btrfs subvol snapshot /.snapshotA /.current > > 4. reboot > > c) rsync > > 1. rsync $options /.snapshotA /.current > > 2. reboot > > Depending on how broken the setup is, I'd probably go for the btrfs > sub snap ./__snapshots/@oldsnap ./@current approach. Is there a technical reason behind this ? > If it is very broken (as in not bootable), then a temporary boot into > a readonly snapshot might be required. This is quite easy to do in > the grub menu, changing the boot parameter. I've also heard of > symlinking to the actual subvolume you want to use, and resymlink it > when an older snapshot is desired. Just to make it clear, i don't have broken system and have full control. I am interested in strategies and reasoning. -- 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
