-
Notifications
You must be signed in to change notification settings - Fork 144
Open
Description
Describe the bug
When the destination filesystem is a btrfs raid1 disk array, selecting 'Settings - Location' in the Timeshift GUI results in a disk space error, despite there being plenty of space available.
To Reproduce
Steps to reproduce the behavior:
- Create a mirrored btrfs filesystem:
mkfs.btrfs -d raid1 -m raid1 /dev/sdb /dev/sde - Mount the primary disk on /backup:
mount /dev/sdb /backup - Configure Timeshift to use rsync with /dev/sdb as destination.
- Start Timeshift and select 'Settings - Location'
- Timeshift reports 'Not enough disk space (<1,000 MB)' even though there is plenty of space in the btrfs filesystem: (Image1)
- Click OK and it reports '0 B Available /dev/sde': (Image2)
- It has selected the mirror disk rather than the primary.
- Quit out of Timeshift, select 'No' to 'Select another device?' and restart it.
- It correctly reports '1.2 TB Available /dev/sdb': (Image3)
The confusion probably arises from both disks having the same UUID, but they have different UUID_SUBs, as reported by blkid:
root@mint21:~# blkid /dev/sdb /dev/sde
/dev/sdb: UUID="6b5f43c8-e1c1-4aa8-8b9e-ea70936bdfda" UUID_SUB="f238470e-8b33-4a30-9d64-6b2d70ec2e79" TYPE="btrfs"
/dev/sde: UUID="6b5f43c8-e1c1-4aa8-8b9e-ea70936bdfda" UUID_SUB="b773913c-213f-4355-890a-6483137c9f42" TYPE="btrfs"
root@mint21:~# btrfs filesystem show /backup
Label: none uuid: 6b5f43c8-e1c1-4aa8-8b9e-ea70936bdfda
Total devices 2 FS bytes used 701.90GiB
devid 1 size 1.82TiB used 764.01GiB path /dev/sdb
devid 2 size 1.82TiB used 764.01GiB path /dev/sde
Expected behavior
Timeshift Settings - Location should show the correct filesystem available capacity.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels


