Skip to content
This repository has been archived by the owner on Oct 16, 2022. It is now read-only.

Disabling qgroups makes Timeshift misbehave (snapshots not deleted on first try) #865

Closed
ShrirajHegde opened this issue Feb 13, 2022 · 2 comments

Comments

@ShrirajHegde
Copy link

Describe the bug
Enabling qgroups freezes the system during scheduled snapshots. After Disabling qgroups, Timeshift still runs btrfs qgroups destroy which errors out.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Settings->Users'
  2. Disable 'enable qgroups'
  3. run btrfs quota disable mount-point
  4. Restart timeshift
  5. Try to delete a snapshot, Error message:
Destroying qgroup: 0/333
E: Failed to destroy qgroup: '0/333'
E: Failed to remove snapshot: 2022-02-13_00-13-34
------------------------------------------------------------------------------

E: ERROR: can't list qgroups: quotas not enabled

E: btrfs returned an error: 256
E: Failed to query subvolume quota

Expected behavior
When btrfs qgroup is disabled and enable qgroup is disabled in timeshift, do not run any btrfs qgroup command. Also, it would be great to have the error output in the window.

do not run any btrfs qgroup command

Or

Additionally, a warning about system freeze during snapshot would be useful here
image

Screenshots

System:

  • Fedora 35 (With @ and @home subvolumes)
  • Desktop : Gnome
  • Application Version : 29.09.1

Also, can someone tell me what is the exact purpose of btrfs qgroup destroy when timeshift doesn't use btrfs qgroup create?

@l0rdg3x
Copy link

l0rdg3x commented Mar 20, 2022

Same as #680

@GenocideStomper
Copy link

Did the commit 4b1af6d disable or enable qgroup functionality permenently, along with hiding the option?

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

No branches or pull requests

3 participants