Why is the ubuntu based partitioning followed?

Run the btrfs command above:

sudo btrfs subvolume list /

snapshots are subvolumes

1 Like

Yes but my root is not named @. How did jt take a snap if I don't have a @ it Def took a snap of stuff inside my root.

What does it show? "@" or "root"?


You would also see the timeshift snapshots if it took one.


Think of subvolumes/snapshots/@s as containers. @root contains /, @home contains /home, etc.

Other subvolumes/snapshots/@s contain copies of what was in @root, for instance, to be the most local of all local backups.

The nitty gritty: btrfs Wiki

1 Like

The Ubuntu-style "@" are only needed by Timeshift. If Garuda gets rid of Timeshift I would be happy. The same purpose could be filled within Garuda Assistant, it already has a btrfs category.

for updates, a garuda-hook for btrfs snapshot would be enough, no need of Timeshift-autosnap. Timeshift is designed with Ubuntu in mind, it has its own limitation of taking snapshot, that is "@" and "@home".

If Garuda gets rid of Timeshift, this problem would vanish. A few more buttons in Garuda Assistant could make Timeshift-independent.


According to my logic we would just need to fork tomeshift, ask the owner to modify and use it, the ubuntu based convention is used for identification of partitions only right? If we re make the partition locator we won't need to use the @ convention. Am I correct?

So, I personally don't use @ style subvolumes(or timeshift) on my own systems. That being said, I don't really understand why people get so concerned about the @ naming convention. It neither helps nor hurts anything. What reason is there to not use that naming convention? What advantage would it bring?

A few things here:

  • Timeshift is doing more than just taking snapshots around updates, it is also taking periodic snapshots and pruning snapshots based on rules. While Garuda could build infrastructure to replace all that, what would be the actual benefit to make developing and maintaining all the worth it when there are already tools that do those things?
  • Timeshift is a horrifically limited tool when it comes to btrfs, it basically limits you to only being able to take snapshots of certain volumes for system recovery purposes. That being said, within the framework of that one thing, it does it well. Further, it is far easier to use than any of the alternatives out there.
  • Something like snapper is far more flexible but it is more complicated.

From my perspective, that isn't a "problem". However, if it is a problem, it is dolphin that has a problem, not timeshift.


I suppose you could fork timeshift but I would have two questions somewhat similar to the above.

  • Why do you care so much about whether or not the subvolume names have @ symbols in them?
  • Timeshift isn't the only tool for taking btrfs snapshots, why not just use a different one if timeshift doesn't meet you needs?

I just replied to what samexpert said I don't have a problem with tkmeshift

1 Like

"If a program doesn't compile, keep deleting lines until it does. At some point the program will compile."



I agree. I added this as a little (very little) benifit, the Garuda team may save few posts in future. For me it is 0 problem, since I don't use that shortcut button at all.

I think I did not describe properly, sorry for that. I'm not highlighting "@" as a problem, to make it clear, I'm fine with it. I even created the same "@" structure in my phone by myself, inspired by the same OpenSUSE idea. I like the way and am happy with it :slight_smile:

Why I asked not to depend on Timeshift:


About Timeshift, there are some problems:

  1. Browse snapshot does not work in KDE. Till now I never could by pressing Browse button.
  2. Remember the Timeshift bug that created number of posts here and SKIP_AUTOSNAP=1 was suggested?
  3. It is creating Qgroups automatically which is not recommended by Arch Wiki which says performance problems may occur.

Currently I don't use Timeshift as I am somewhat comfortable with btrfs.

This is an alternative I can suggest... Feel free to ignore it, since I'm still new and learning it, so way far from being an expert in it :slight_smile:

1. For taking automatic snapshots, a garuda-hook, containing this command:

btrfs subvolume snapshot /

2. For browsing snapshots, opening the snapshot folders (xdg-open) created by btrfs tool. If a user wants to delete a snapshot, deleting the snapshot folder would be the same.

3. For automatic snapshot (a Timeshift's feature as @dalto said) from time to time: A check mark in Garuda Assistant to enable the systemd timer.

4. For restoring to a snapshot, just mv the current subvolume to the date & time, and the snapshot to ("@" maybe?)

Took help from SysadminGuide - btrfs Wiki


@ volumes, subvolumes demonstrate the fluidity of the BTRFS. If you grok it (and I don't) you can setup all sorts of nested stuff. I dunno how much stuff I've read on it, but it must be a lot if my bookmarks are anything to judge.

It's particularly handy with some server RAID setups. Or so I hear.

All I really do know about BTRFS, is the more I learn about it the more confused I get. It's really not made for 60-70 year olds who have a loose grasp (at best) on anything virtual or fluid. Hell, I can't even remember how to set the time on the microwave, and that's real world hardware. :wink:

But I did save a bundle at GEICO! :wink:


Removing the check mark in the Timeshift/settings/users tab easily disables this option. I keep it disabled, but it is helpful if you are trying to manage your storage space accurately.

1 Like

IMHO, the real problem is the bad (no simplified version) documentation. It makes it more difficult than it actually is.

Because I'm an RTFM type, I just don't use it, until I do. :stuck_out_tongue_winking_eye:


Even I tried this, at the very first after a clean install, but autosnap enabled it again. I couldn't find out how to disable it permanantly. I remember a message on update saying "Warning: Quota is not enabled", "Enabling Qgroups" or something similar, don't remember accurately.

Also, I have enabled SKIP_AUTOSNAP in /etc/timeshift-autosnap.conf, I think this improved a little in performance, but can't say exactly, since I'm not sure about my hard drive.

Cgroups. Don't ask me what they are but my BIOS has 'em (optional) and there are cgroup-related packages in the repos. Sum total of my knowledge of cgroups.

Oops! And Red Hat uses 'em, from my experience. :wink:

1 Like

I have it disabled. :wink:

BTRFS quota is automatically re-enabled if I disable it manually?


btrfs-transcation at 100% CPU causes processes to hang for several minutes


How does enabling btrfs quotas impact the system?

Check if btrfs quota is enabled, and find how much space a btrfs snapshot is taking up:

sudo btrfs qgroup show /

You recieve this if not enabled:

ERROR: can't list qgroups: quotas not enabled

First disable btrfs quotas:

sudo btrfs quota disable /

In the "Users" tab of the Timeshift "Settings" menu, disable "Enable BTRFS qgroups (recommended)". You can also do this directly from Timeshift's config file.

Timeshift's configuration file has an option btrfs_use_qgroup that can be changed to prevent quotas from being automatically re-enabled by Timeshift.

Open /etc/timeshift/timeshift.json with a text editor:

Search for the following setting:

"btrfs_use_qgroup" : "true",

Change : "true", to : "false",

/etc/timeshift/timeshift.json contents:

  "backup_device_uuid" : "6cf7ad76-31ae-437b-8e11-ed4046bfe754",
  "parent_device_uuid" : "",
  "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" : "false",
  "schedule_monthly" : "false",
  "schedule_weekly" : "false",
  "schedule_daily" : "false",
  "schedule_hourly" : "false",
  "schedule_boot" : "false",
  "count_monthly" : "2",
  "count_weekly" : "4",
  "count_daily" : "5",
  "count_hourly" : "5",
  "count_boot" : "5",
  "snapshot_size" : "0",
  "snapshot_count" : "0",
  "date_format" : "%Y-%m-%d %H:%M:%S",
  "exclude" : [],
  "exclude-apps" : []

Search and yee will find. :male_detective:


Well, hell, I guess they are qgroups...why am I confusing the two? I'm old. I should know better. Thanks loads, people. :wink:

Note To use qgroup you need to enable quota first using btrfs quota enable command.

Copy from man pages