teejee2008 / timeshift

System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
GNU Lesser General Public License v3.0
4.69k stars 282 forks source link

Timeshift with BTRFS on Arch #729

Open jannis3005 opened 3 years ago

jannis3005 commented 3 years ago

Hi,

I'm trying to setup Timeshift Backup using BTRFS on Arch with Encryption. I've created a btrfs root and the subvolumes @ and @home. Those are mounted and working fine. However, Timeshift tells me that layout is unsuported, even though I though this is the only supported layout for timeshift? Looking at the code, as long as I don't include the @home subvol, it should work as long as I have any @ subvol.

image

Any idea on what I'm doing wrong?

wmutschl commented 3 years ago

Could you post your timeshift configuration file as well as the output of blkid and your fstab to check whether the UUID are correct in timeshift?

jannis3005 commented 3 years ago
Timeshift Config
{
  "backup_device_uuid" : "d232a098-8123-4899-a81b-c2e34adf022c",
  "parent_device_uuid" : "5139ee26-e553-450c-9563-05f6a472a4bb",
  "do_first_run" : "false",
  "btrfs_mode" : "true",
  "include_btrfs_home_for_backup" : "false",
  "include_btrfs_home_for_restore" : "false",
  "stop_cron_emails" : "true",
  "btrfs_use_qgroup" : "true",
  "schedule_monthly" : "false",
  "schedule_weekly" : "false",
  "schedule_daily" : "true",
  "schedule_hourly" : "false",
  "schedule_boot" : "false",
  "count_monthly" : "2",
  "count_weekly" : "3",
  "count_daily" : "5",
  "count_hourly" : "6",
  "count_boot" : "5",
  "snapshot_size" : "0",
  "snapshot_count" : "0",
  "date_format" : "%Y-%m-%d %H:%M:%S",
  "exclude" : [
    "/root/**",
    "/home/jannis/**"
  ],
  "exclude-apps" : []
}
blkid --label system
/dev/mapper/cryptsystem
lsblk --fs
NAME            FSTYPE      FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINT
nvme0n1                                                                                           
├─nvme0n1p1     vfat        FAT32 BOOT        7ED4-DE38                             900,6M    12% /boot
├─nvme0n1p2                                                                                       
├─nvme0n1p3     ntfs                          6ECAD3D8CAD39B23                                    
├─nvme0n1p4     crypto_LUKS 2     cryptsystem 5139ee26-e553-450c-9563-05f6a472a4bb                
│ └─cryptsystem btrfs             system      d232a098-8123-4899-a81b-c2e34adf022c    1,1T    18% /home
└─nvme0n1p5                                                                                       
  └─cryptswap   swap        1     cryptswap   99ba785f-4cf7-422b-9822-7c4630ea3a8a                [SWAP]
fstab
# /dev/mapper/system UUID=d232a098-8123-4899-a81b-c2e34adf022c
LABEL=system            /               btrfs           rw,noatime,compress=lzo,ssd,space_cache,subvolid=256,subvol=/@,subvol=@     0 0
# /dev/nvme0n1p1 UUID=7ED4-DE38
LABEL=BOOT              /boot           vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro       0 2
# /dev/mapper/system UUID=d232a098-8123-4899-a81b-c2e34adf022c
LABEL=system            /home           btrfs           rw,noatime,compress=lzo,ssd,space_cache,subvolid=257,subvol=/@home,subvol=@home     0 0
# /dev/mapper/swap UUID=51018adb-f6c4-4e27-be7f-39bf93f20bc8
/dev/mapper/cryptswap           none            swap            sw      0 0
sfaucheux commented 3 years ago

I just add the same problem on a fresh arch install. Using UUID= instead of LABEL= to identify the partition in /etc/fstab solved the problem for me.