On Sun, 8 May 2016 16:40:22 +0200, Adam Borowski <kilob...@angband.pl> wrote: >On Sun, May 08, 2016 at 02:20:45PM +0200, Marc Haber wrote: >> Tracking sid is a good idea if you can debug and fix breakages. If you >> want to be warned for disruptions, use something that we actually >> released. > >Another way is to use btrfs (or zfs or perhaps LVM snapshots): whenever >something goes south in a way that's not trivial to recover, you can >restore with a couple commands and reboot. And if unbootable because, >for example, someone removed support for your CPU, you boot with >subvol=backups/sys-2016-05-07.
btrfs has suffered severe regressions since kernel 4.4, with the btrfs upstream community only offering advice like "don't use so many snapshots" or "say goodbye to existing snapshots, backup, format with latest btrfs-tools, restore". This is, unfortunately, not a filesystem that I'd trust to keep my data, despite not having _lost_ actual data other than snapshots, but those bugs and the suggested remedies do not fit my expectations. Greetings Marc -- -------------------------------------- !! No courtesy copies, please !! ----- Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
