[Solved] Where can i find timeshift wiki ?

[hallow field]

The github repo is archived in 2017. Is there no other update wiki ?

[grave solar]

Apparently linuxmint did not bother to maintain a wiki after taking over development of timeshift.

What part of this program confuses you?

[hallow field]

Thanks for replying .. Actually on my main system i used btrfs but wasn't aware of subvolume and i was looking over this whole day today.

So instead of messing up my main system , i booted laptop with external hdd and installed arch with btrfs subvolume.

Can you please tell me if i have setted it up correctly by seeing this lsblk and fstab .. and if you any btrfs command that can verify it then please let me know

[ornate socket]

Senatvs Popvlvsqve Romanvs received a thank you cookie!

[hallow field]

[phoenix@archbtrfs ~]$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   785G  0 part 
├─sda2   8:2    0   512M  0 part /efi
├─sda3   8:3    0     8G  0 part [SWAP]
├─sda4   8:4    0    50G  0 part /var_log
│                                /.snapshots
│                                /
└─sda5   8:5    0    88G  0 part /home

[phoenix@archbtrfs ~]$ cat /etc/fstab 
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb4
UUID=377540d2-228e-456a-9dcb-4c2b05596adc    /             btrfs         rw,noatime,compress=lzo,space_cache=v2,subvolid=256,subvol=/@    0 0

# /dev/sdb5
UUID=c888eb57-62d4-4e66-a79e-14cfd0b7493d    /home         btrfs         rw,noatime,compress=lzo,space_cache=v2,subvolid=256,subvol=/@home0 0

# /dev/sdb4
UUID=377540d2-228e-456a-9dcb-4c2b05596adc    /.snapshots    btrfs         rw,noatime,compress=lzo,space_cache=v2,subvolid=258,subvol=/@snapshots    0 0

# /dev/sdb4
UUID=377540d2-228e-456a-9dcb-4c2b05596adc    /var_log      btrfs         rw,noatime,compress=lzo,space_cache=v2,subvolid=259,subvol=/@var_log    0 0

# /dev/sdb2
UUID=7A03-A43A          /efi          vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro    0 2

# /dev/sdb3
UUID=eb2200c6-bf3d-4203-86fc-f0608c3eb258    none          swap          defaults      0 0

[grave solar]

So instead of messing up my main system , i booted laptop with external hdd and installed arch with btrfs subvolume
Is this an experiment?

[hallow field]

yes , actually my original system lsblock is like this --->

[phoenix@archbtrfs ~]$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0   785G  0 part 
├─sda2   8:2    0   512M  0 part /efi
├─sda3   8:3    0     8G  0 part [SWAP]
├─sda4   8:4    0    50G  0 part /
└─sda5   8:5    0    88G  0 part /home

and i was confused with the whole .. subvolume ..mounting concept ...

so i followed https://www.youtube.com/watch?v=Xynotc9BKe8&pp=ygUPYnRyZnMgYXJjaGxpbnV4 ( now i realise he actually made newer video for the same ) and i got like gits of it ..

so on sdb4 i created @ , @snapshots
and on sdb5 i created @home ( i have seprate home partition )

mounted then using fstab ...
home and root seems good . ( is this how it should be done ? )

But i am not sure wether @snapshot is being used or not .. how to confirm .. /.snapshot seems to be empty but in timeshift i have a backup created

[grave solar]

Regarding the Selected snapshot device is not a system disk error you received earlier, it appears that Timeshift requires the system root to be on a subvolume called '@'.

        var root_path = path_combine(mount_paths["@"],"@");
        log_debug("root_path=%s".printf(root_path));
        log_debug("btrfs_mode=%s".printf(btrfs_mode.to_string()));
        if (btrfs_mode){
            if (!dir_exists(root_path)){
                status_message = _("Selected snapshot device is not a system disk");
                status_details = _("Select BTRFS system disk with root subvolume (@)");
                status_code = SnapshotLocationStatus.NO_BTRFS_SYSTEM;
                log_debug(status_message);
                return false;
            }
        }

[grave solar]

The BTRFS subvolume can also eliminate the need for, and most of the benefits of, a separate home partition.

[hallow field]

sorry i didn't mentioned any error ( even though i got one - saying - read only snaphot or something ) but i didn't get this error

[hallow field]

really .. thats good to know .. then i will move back to single partition

[grave solar]

#1148501656246427648 message

[hallow field]

how to run this code

[grave solar]

No, it's the source code of timeshift

[hallow field]

i created a script.sh ... and used chmod +x

[hallow field]

lol .. my bad

so is my setup correct ?

[grave solar]

If you can boot it, there is no problem at all.

[hallow field]

whats the use of @snapshot subvolume ?

and how to check @snapshot is working as intended

[grave solar]

As far as I know, Timeshift stores snapshots in /timeshift/snapshots/ by default, this is probably the result of a custom setup, if you're following some random videos I wouldn't know.

You can list all the subvolumes in a filesystem using btrfs subvolume list path/to/fs.

[hallow field]

i didn't changed any config of timeshift .. the video was using snapper

sudo btrfs subvolume list /
[sudo] password for phoenix: 
ID 256 gen 262 top level 5 path @
ID 258 gen 137 top level 5 path @snapshots
ID 259 gen 142 top level 5 path @var_log
ID 260 gen 27 top level 256 path var/lib/portables
ID 261 gen 28 top level 256 path var/lib/machines
ID 262 gen 191 top level 5 path timeshift-btrfs/snapshots/2023-09-05_23-35-49/@

[grave solar]

They are utterly different things. Are you currently using Snapper or Timeshift?

[hallow field]

timeshift ... i was using video as a reference material . and only followed it till subvolume creation and mounting

do you use timeshift ? should i move timeshift backup to @snapshot ? ... as there is no guide its really hard to know about this ...

Do you any documentation that i can read

[grave solar]

As has been said, the two are not related.

You should not use Snapper's documentation or tutorial to "set up" timeshift, as their configurations are fundamentally different.

[hallow field]

ok .. i think things are working fine now and i will improve upon this later ...

one last thing this screenshot is from arch-wki . can you confirm wether my setup is inline with the tip ?

[hallow field]

ok got it .. @snapshot is part of snapper guide ..

[grave solar]

UUID=377540d2-228e-456a-9dcb-4c2b05596adc / btrfs rw,noatime,compress=lzo,space_cache=v2,subvolid=256,subvol=/@ 0 0
Yes

[hallow field]

time shift only recommends @ and @home

Thank you for helping.

[Solved] Where can i find timeshift wiki ?

sorry to extend this .. but what mount flags would you recommend for btrfs ?

[bronze egret]

your /var/log subvol mount is wrong

[bronze egret]

because it can only handle those

[hallow field]

on my main system i will just use @ and @home

[bronze egret]

if you want some thing that supports more subvol and can use other names then use snapper

[hallow field]

ok

which flags should i use to mount btrfs @worthy sphinx any recommendation ?

[bronze egret]

compress

[ancient wing]

compress-force=zstd:3,discard=async

[hallow field]

also , which is better timeshift or snapper ? we even have docs for snapper on archwiki

[bronze egret]

change the level of compression depending if how fast your drive is

so to not bottleneck them much

[bronze egret]

snapper is more flexible
timeshift is more simple

[ancient wing]

i use btrbk

[hallow field]

will look into it .. how did you found it .. there is no mention of anything other than snapper on archwiki

[bronze egret]

i found that one through pacman funnily enough

[ancient wing]

it is mentioned here

btrbk is very basic

it doesn't do automatic restoring

[bronze egret]

wait you can send hyperlinks on discord now?

[ancient wing]

$ cat /etc/btrbk.conf
timestamp_format        long
snapshot_preserve_min   latest
snapshot_preserve       no
target_preserve_min     24h
target_preserve         24h 7d 4w 2m

volume /media/ssd_root
  snapshot_dir btrbk_snapshots
  target /media/hdd_root/btrbk_snapshots
  subvolume @
  subvolume @boot
  subvolume @home

then i just run btrbk with a cron job

[ancient wing]

yes

[text](url)

[bronze egret]

sick!!

fuck i forgot to remove embed

[ancient wing]

you can't remove embed before sending

[bronze egret]

now that's better

i can

<>

[ancient wing]

you surround the link with angle brackets?

[bronze egret]

yes

[ancient wing]

test

[bronze egret]

the link

like (<a>)

[hallow field]

i think i will go with snapper .. any disadvantage that i should know ?

[ancient wing]

oh nice

[bronze egret]

if you might be lengthy to setup like around 5 mins
but that's because i have an outlandish subvol setup

[hallow field]

if you don't mind can i get a screenshot ? did you follow any guide so that i can understand the reasoning and benefits of those subvoulumes

[ancient wing]

subvolumes just allow you to mount and make snapshots of them individually

my subvols are @, @home, and @boot

but some people do more

[hallow field]

i am confused .. if you make more subvolumes and don't restore all at same time won't it create conflict ? and if in the end every subvolume is going to be restored at same time then dosen't create only @ is enough as it wil restore everything at once

[bronze egret]

some parts dont create conflicts and there are some parts of the filesystem not even worth rolling back/snapshotting
like /var/log
rolling back /home or root wont create conficts with each other

the thing why mine is outlandish is that i also seperate my different arch installations per subvolume basis instead of each own filesystems

[hallow field]

ohh nice , i will have to learn mutiple os using subvolume later ..

Thanks for all the help guys.

[ancient wing]

i have a full gentoo installation inside a gentoo subvol of my main arch install

and i can boot it directly with grub

[bronze egret]

i have like 3 arch installs 1 being readonly for overlayfs root 💀

the readonly one is where i test packages
i dont even know why im still keeping the 2nd i barely even use it

[ancient wing]

lol

[hallow field]

lets say ,, i have only one partition dev/sdb2 and create only one subvolume @ , and don't create @home subvolume . if i create backup , will contents of @/home will be backed up too ? if i don't want to backup home partition , do i gotta create a subvolume for it .

And what if my home partition is on dev/sdb3 , will it change anything above ?

What is the notation used when reffereing to directory in this btrfs subvolume case ?

Previously i just had to use / root , /home and say that /dev/sd4 is mounted on /home .
What is notation with subvolumes ?

[ancient wing]

If /home is just a directory in the @ subvolume, then yes, backups of the the @ subvolume will contain /home so it will be backed up.
If your /home is on a different partition then you'll have to back it up separately.

[ancient wing]

Not sure exactly what you mean. It's convention to name subvolumes with an @ at the beginning to make them more distinguished from directories

though they can be accessed as directories

you could, for example, create a subvolume under the @ subvolume called home and it would appear as a regular directory

but it's generally a good idea to name them something else and mount them to the correct places

[hallow field]

What if /home is inside a subvolue @home .. then backup of @ subvolume won't include @home subvolume . right ?

[ancient wing]

if your subvolumes are like this

Subvolume              Mount point
@                      /
@home                  /home

then no, a backup of @ will not include your home directory

you would need to back up @ and @home

[hallow field]

ok got it .. thank you

[ornate socket]

឵឵ received a thank you cookie!