Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Max Chernoff <git@maxchernoff.ca>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu Wenruo <wqu@suse.com>,
	 linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: docs: update the qgroup performance hit
Date: Sat, 02 May 2026 04:11:43 -0600	[thread overview]
Message-ID: <e3a5fe230cb90d08acd6b0d99dc3477cfe7a2314.camel@maxchernoff.ca> (raw)
In-Reply-To: <2da00f33-9325-4bd8-b874-37b0ef204f7f@gmx.com>

Hi Qu,

On Sat, 2026-05-02 at 19:00 +0930, Qu Wenruo wrote:
> 在 2026/5/2 17:06, Max Chernoff 写道:
> > Would it maybe be worth adding something like the following?
> >
> >      If quota support is absolutely required for a filesystem with many
> >      snapshots, then "simple quotas" (``squota``) should be preferred
> >      over "quota groups" (``qgroups``).
> >
> > I've never used simple quotas myself, so I have no idea if that is
> > actually true, but the documentation suggests that that's the case at
> > least.
>
> Squota has one special quirk that makes it pretty anti-instinctual, thus
> I intentionally skipped that recommendation.
>
> E.g. We have subvolume 256, which is the initial subvolume, have around
> 128MiB data. Then a snapshot of subvol 256 is created, that snapshot has
> the subvolid 257.
>
> Now we have something like: (squota has no distinguish between reference
> and exclusive, it treat them all as semi-exclusive)
>
>    Subvolid         Reference/Exclusive
>         256         128MiB
>         257         0
>
> Here we ignore metadata to make it easier to explain.
>
> If you know subvol 257 is a snapshot of 256, it makes sense since there
> is no new data in subvol 257 yet.
>
> Then if subvol 256 is deleted, things go ugly immediately, after subvol
> 256 fully deleted, the result is:
>
>    Subvolid         Reference/Exclusive
>         256         128MiB
>         257         0
>
> Nothing changed.
>
> I do not believe most end users expect results like this at all.

Ok yeah, I agree that that would probably be too confusing to recommend
to unsuspecting users. Thanks again for the explanation.

-- Max

      reply	other threads:[~2026-05-02 10:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 10:43 [PATCH] btrfs-progs: docs: update the qgroup performance hit Qu Wenruo
2026-05-01 20:21 ` Neal Gompa
2026-05-01 22:59   ` Qu Wenruo
2026-05-02  7:36 ` Max Chernoff
2026-05-02  9:30   ` Qu Wenruo
2026-05-02 10:11     ` Max Chernoff [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e3a5fe230cb90d08acd6b0d99dc3477cfe7a2314.camel@maxchernoff.ca \
    --to=git@maxchernoff.ca \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox