start:timeshift
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| start:timeshift [2023/08/29 19:15] – peter | start:timeshift [2024/11/21 22:07] (current) – admin | ||
|---|---|---|---|
| Line 30: | Line 30: | ||
| Addendum 2: There was a short period where you had to specify space_cache=v2 but with release of Debian 12 this is no longer true. Simply specifying space_cache defaults to v2 so it is no longer required to specify the =v2 anymore once again. You can 100% just put space_cache and that is enough. | Addendum 2: There was a short period where you had to specify space_cache=v2 but with release of Debian 12 this is no longer true. Simply specifying space_cache defaults to v2 so it is no longer required to specify the =v2 anymore once again. You can 100% just put space_cache and that is enough. | ||
| - | Ok So we just installed Debian stable if you followed the install guide and before updating to Debian testing it would be advantageous to first get timeshift going so that we can roll back no matter what without starting again, even if we totally break the system and its completely borked. **It is possible to create an @home during install but I wanted to show you that fixing a mistake is possible as it is important to know that you should never have to reinstall to fix a problem. All problems can be fixed with enough know how, as in linux everything is just a file on a disk, so if you edit the correct files on the disk and create the correct things then it must work. This is an inescapable truth about linux in general.** | + | Ok So we just installed Debian stable if you followed the install guide and before updating to Debian testing it would be advantageous to first get timeshift going so that we can roll back no matter what without starting again, even if we totally break the system and its completely borked. **It is possible to create an @home during install but I wanted to show you that fixing a mistake is possible as it is important to know that you should never have to reinstall to fix a problem. All problems can be fixed with enough know how, as in linux everything is just a file on a disk, so if you edit the correct files on the disk and create the correct things then it must work. This is an inescapable truth about linux in general. Everything is a file. The only reason something is broken is because you dont have the knowledge on what file(s) to edit to fix it. Never forget this fact. ** |
| So lets first review that our @ subvolume is working after installing and everything is as we expect. Obviously we want the @ subvolume in fstab on the / mountpoint during install but what does that mean? How do we access it? | So lets first review that our @ subvolume is working after installing and everything is as we expect. Obviously we want the @ subvolume in fstab on the / mountpoint during install but what does that mean? How do we access it? | ||
| Line 67: | Line 67: | ||
| Well first lets make a new subvolume for @ home: | Well first lets make a new subvolume for @ home: | ||
| Now copy and paste the line that looks like this: | Now copy and paste the line that looks like this: | ||
| - | UUID=f0c8474c-e0dd-489a-af83-79b61e879de5 / | + | UUID=f0c8474c-e0dd-489a-af83-79b61e879de5 / |
| Note: ssd option for btrfs is depreciated and not used anymore. Dont forget at the beginning of the guide it mentioned using space_cache now. | Note: ssd option for btrfs is depreciated and not used anymore. Dont forget at the beginning of the guide it mentioned using space_cache now. | ||
| Line 103: | Line 103: | ||
| < | < | ||
| - | mv / | + | mv / |
| chown -R peter / | chown -R peter / | ||
| </ | </ | ||
| Line 139: | Line 140: | ||
| That is around 20 which is fine and give you plenty to look back on. Anything else you should refer to your backup set. Another thing to note is the automatic backups per schedule wont happen if you have Timeshift open for some reason. You must leave Timeshift closed. Also, the hourly always happen on the hour, so you will need to wait for an hour to pass + whatever was remaining for the current hour. So if the time was 9:23, your first hourly backup would be at 11:00. The reboot schedule also seems to have a delay on it so if you reboot and immediately open Timeshift you wont see any snapshot. Just go get a coffee or something and leave it like 15 minutes after a reboot or check after 2 hours have passed to see auto snapshots getting made. It doesn' | That is around 20 which is fine and give you plenty to look back on. Anything else you should refer to your backup set. Another thing to note is the automatic backups per schedule wont happen if you have Timeshift open for some reason. You must leave Timeshift closed. Also, the hourly always happen on the hour, so you will need to wait for an hour to pass + whatever was remaining for the current hour. So if the time was 9:23, your first hourly backup would be at 11:00. The reboot schedule also seems to have a delay on it so if you reboot and immediately open Timeshift you wont see any snapshot. Just go get a coffee or something and leave it like 15 minutes after a reboot or check after 2 hours have passed to see auto snapshots getting made. It doesn' | ||
| - | So hit next and on the next screen you can go ahead and tick the " | + | So hit next and on the next screen you can go ahead and tick the " |
| Once you are done selecting all your options just click finish. You can create a manual snapshot by clicking the create button as a test. | Once you are done selecting all your options just click finish. You can create a manual snapshot by clicking the create button as a test. | ||
| Line 219: | Line 220: | ||
| {{: | {{: | ||
| - | There you go! Now you know how to run around and completely break your Linux install and never not be able to revert. You will always have a working Debian to boot into by reverting back to the time before you broke it. Now lets get on with setting up more fun an experimental stuff happy in the knowledge we cannot fail, by design. | + | There you go! Now you know how to run around and completely break your Linux install and never not be able to revert. |
| In the guide if things break I dont use Timeshift, instead I try to show you how to fix them so that you can learn what has happened, but we always have Timeshift to fall back on if need be. | In the guide if things break I dont use Timeshift, instead I try to show you how to fix them so that you can learn what has happened, but we always have Timeshift to fall back on if need be. | ||
| Line 232: | Line 233: | ||
| Once you have no snapshots and no qgroups at all then snapshotting seems repaired and wont hang the system although you can get hangs if you have too many snapshots or some issue occurs with them again (typically caused by unclean shutdown etc). They are troublesome but I find they dont cause me an issue if everything is clean and nothing is orphaned etc. | Once you have no snapshots and no qgroups at all then snapshotting seems repaired and wont hang the system although you can get hangs if you have too many snapshots or some issue occurs with them again (typically caused by unclean shutdown etc). They are troublesome but I find they dont cause me an issue if everything is clean and nothing is orphaned etc. | ||
| + | |||
| + | Also note qgroups is an older issue that is no longer a problem (as they are disabled by Debian 12 onwards anyway). | ||
start/timeshift.1693336553.txt.gz · Last modified: 2023/08/29 19:15 by peter
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
