setup;
Summary
Drives:
Local Storage: total: 1.82 TiB used: 69.22 GiB (3.7%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: rev: 033 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD10JPVT-75A1YT0
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
type: HDD rpm: 5400 serial: rev: 1A01 scheme: GPT
Partition:
ID-1: / raw-size: 140.44 GiB size: 137.98 GiB (98.25%)
used: 15.52 GiB (11.2%) fs: ext4 dev: /dev/sda8 maj-min: 8:8
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 25.5 MiB (26.5%) fs: vfat dev: /dev/sda2 maj-min: 8:2
ID-3: /home raw-size: 200 GiB size: 195.8 GiB (97.90%) used: 2.22 GiB (1.1%)
fs: ext4 dev: /dev/sda9 maj-min: 8:9
NAME MOUNTPOINT LABEL FSUSED FSAVAIL FSUSE% FSSIZE UUID
sda
├─sda2 /boot/efi 25.5M 70.5M 27% 96M 4E3C-18CB
├─sda8 / MANJARO-SSD 15.5G 115.8G 11% 138G e0d878c7-a550-4927-b2b9-
└─sda9 /home RESERVE-SSD 2.2G 183.6G 1% 195.8G 5c3528c3-550b-4b0d-a071-sdb
├─sdb9 /mnt/reserve RESERVE 51.5G 75.6G 38% 133.9G c89752c9-61aa-47b9-a922-
so yeah i installed timeshift, setup with rsync and snapshots are stored on (sdb9) my hard drive. i use that mount(fstab mounted) to also keep my other downloads.
problem is when i just launch timeshift it messes up mounts;
$ mount | grep /dev/sdb9
/dev/sdb9 on /mnt/reserve type ext4 (rw,nosuid,nodev,noatime,x-gvfs-show)
$ sudo timeshift-gtk
App config loaded: /etc/timeshift/timeshift.json
Mounted '/dev/sdb9' at '/run/timeshift/backup'
App config saved: /etc/timeshift/timeshift.json
$ mount | grep /dev/sdb9
/dev/sdb9 on /mnt/reserve type ext4 (rw,nosuid,nodev,noatime,x-gvfs-show)
/dev/sdb9 on /run/timeshift/backup type ext4 (rw,relatime)
the problem is now when i delete stuff in dolphin, it is moved from HDD to SDD(trash) because the second mount; /dev/sdb9 on /run/timeshift/backup type ext4 (rw,relatime) is in effect.
sudo mount -a
does not fix it. right now it is fixable only by reboot.