Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catch-22 with Fedora and BTRFS #368

Open
ric-m opened this issue Nov 16, 2024 · 1 comment
Open

Catch-22 with Fedora and BTRFS #368

ric-m opened this issue Nov 16, 2024 · 1 comment

Comments

@ric-m
Copy link

ric-m commented Nov 16, 2024

Describe the bug
Cannot restore because filesystem doesn't conform to Ubuntu layout standard where prefixes use @

To Reproduce
Steps to reproduce the behavior:

  1. Install Fedora + Timeshift
  2. Volume is BTRFS by default
  3. Snapshots created perfectly
  4. Error message: cannot restore: Unsupported subvolume layout

Expected behavior
Warnings about BTRFS have come true: behaviour is exactly as predicted

Wanted behavior

  1. Want to create snapshots on separate disk formatted as EXT4 as advised in the readme.
  2. therefore have to use rsync (btrfs mode does not permit different device)
  3. different device important in case source drive damaged/corrupted/etc
  4. snapshots created exactly as expected
  5. cannot restore because filesystem subvolumes are not prefixed with @
  6. the catch: cannot use btrfs mode because i am using separate internal disk; cannot restore using rsync method because filesystem does not conform to ubuntu standard.
  7. between a rock and a hard place and no idea how to resolve (really don't want to mess with fedora filesystem)
  8. Is there a way forward or is Timeshift just not for me?

Screenshots
n/a

System:

  • OS: Fedora 41
  • Desktop: KDE Plasma 6
  • Application Version: Timeshift 21.11.2
@10leej
Copy link

10leej commented Dec 30, 2024

@clefebvre this has been a known issue with timeshift basically ever since it added btrfs support.
Will this ever be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants