From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, fdmanana@gmail.com, Qu Wenruo <wqu@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] fstests: btrfs: check qgroup doesn't crash when beyond limit
Date: Sat, 14 Nov 2020 08:09:49 +0800 [thread overview]
Message-ID: <705e1226-2aaf-0d5f-45ed-03b25457e680@gmx.com> (raw)
In-Reply-To: <20201113151946.GY6756@twin.jikos.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1015 bytes --]
On 2020/11/13 下午11:19, David Sterba wrote:
> On Thu, Nov 12, 2020 at 07:50:22AM +0800, Qu Wenruo wrote:
>>>> +$BTRFS_UTIL_PROG quota enable $SCRATCH_MNT
>>>> +$BTRFS_UTIL_PROG quota rescan -w $SCRATCH_MNT >> $seqres.full
>>>> +
>>>> +# Set the limit to just 512MiB, which is way below the existing usage
>>>> +$BTRFS_UTIL_PROG qgroup limit 512M $SCRATCH_MNT $SCRATCH_MNT
>>>
>>> $SCRATCH_MNT twice by mistake, though the command still works and the
>>> test still reproduces the issue.
>>
>> Nope, that's the expected behavior.
>>
>> Btrfs qgroup limit <size> <path>|<qgroupid> <path>
>>
>> The first path is to determine qgroupid, while the last path is to
>> determine the fs.
>>
>> In this particular case, since we're limit the 0/5 qgroup, it's also the
>> as the mount point, thus we specific it twice.
>
> So why didn't you specify 0/5 so it's clear?
>
Oh no, my brain just shorted, and forgot that it's 0/5 fixed for fs tree.
0/5 is indeed much better.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-14 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 11:31 [PATCH] fstests: btrfs: check qgroup doesn't crash when beyond limit Qu Wenruo
2020-11-11 14:38 ` Filipe Manana
2020-11-11 23:50 ` Qu Wenruo
2020-11-13 15:19 ` David Sterba
2020-11-14 0:09 ` Qu Wenruo [this message]
2021-01-11 12:15 ` Filipe Manana
2021-01-11 12:21 ` Qu Wenruo
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=705e1226-2aaf-0d5f-45ed-03b25457e680@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).