From: Josef Bacik <josef@toxicpanda.com>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 5/8] btrfs-progs: simple quotas mkfs
Date: Thu, 13 Jul 2023 16:23:52 -0400 [thread overview]
Message-ID: <20230713202352.GW207541@perftesting> (raw)
In-Reply-To: <19ca469539472675b8cdb0d807e59cbd4e081fd4.1688599734.git.boris@bur.io>
On Wed, Jul 05, 2023 at 04:36:24PM -0700, Boris Burkov wrote:
> Add the ability to enable simple quotas from mkfs with '-O squota'
>
> There is some complication around handling enable gen while still
> counting the root node of an fs. To handle this, employ a hack of doing
> a no-op write on the root node to bump its generation up above that of
> the qgroup enable generation, which results in counting it properly.
>
> Signed-off-by: Boris Burkov <boris@bur.io>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2023-07-13 20:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 23:36 [PATCH 0/8] btrfs-progs: simple quotas Boris Burkov
2023-07-05 23:36 ` [PATCH 1/8] btrfs-progs: document squotas Boris Burkov
2023-07-13 18:02 ` Josef Bacik
2023-07-05 23:36 ` [PATCH 2/8] btrfs-progs: simple quotas kernel definitions Boris Burkov
2023-07-13 20:19 ` Josef Bacik
2023-07-05 23:36 ` [PATCH 3/8] btrfs-progs: simple quotas dump commands Boris Burkov
2023-07-13 20:20 ` Josef Bacik
2023-07-05 23:36 ` [PATCH 4/8] btrfs-progs: simple quotas fsck Boris Burkov
2023-07-13 20:22 ` Josef Bacik
2023-07-05 23:36 ` [PATCH 5/8] btrfs-progs: simple quotas mkfs Boris Burkov
2023-07-13 20:23 ` Josef Bacik [this message]
2023-07-05 23:36 ` [PATCH 6/8] btrfs-progs: simple quotas btrfstune Boris Burkov
2023-07-13 20:25 ` Josef Bacik
2023-07-05 23:36 ` [PATCH 7/8] btrfs-progs: simple quotas enable cmd Boris Burkov
2023-07-13 20:26 ` Josef Bacik
2023-07-05 23:36 ` [PATCH 8/8] btrfs-progs: tree-checker: handle owner ref items Boris Burkov
2023-07-13 20:28 ` Josef Bacik
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=20230713202352.GW207541@perftesting \
--to=josef@toxicpanda.com \
--cc=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.