From: Phillip Susi <psusi@cfl.rr.com>
To: Arne Jansen <sensille@gmx.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC] Subvolume Quota on-disk structures and configuration
Date: Mon, 21 Nov 2011 13:29:38 -0500 [thread overview]
Message-ID: <4ECA9892.9070801@cfl.rr.com> (raw)
In-Reply-To: <4ECA8847.2080905@gmx.net>
On 11/21/2011 12:20 PM, Arne Jansen wrote:
> On 11/21/2011 05:06 PM, Phillip Susi wrote:
>> On 7/10/2011 4:21 AM, Arne Jansen wrote:
>>> btrfs qgroup limit [--exclusive]<size>|none<qgroupid> <path>
>>>
>>>
>>> btrfs qgroup limit 10g /usr
>>>
>>> That should be simple enough for the common use case.
>>
>> Wouldn't that make the syntax above actually be:
>>
>> btrfs qgroup limit [--exclusive]<size|none> [qgroupid]<path>
>
> You don't mean to actually changing the syntax, but adding a better
> explanation or a more precise usage?
What I mean is that your syntax listed <groupid> in angle brackets,
indicating that it is a required argument, but your description seems to
indicate that it is optional, so it should be in square brackets. Also
the size bit I assume was meant to be a required parameter that should
be either a number or the word none, so the angle brackets should
enclose the |none part too.
>> I also have a question about the interactions with groups of groups. Say
>> I have 4 subvolumes: 1, 2, 3, and Z. I group the first 3 volumes and
>> set a limit on them. Now if all 3 volumes share a chunk of space, that
>> space should only count towards the group once, rather than 3 times.
>
> It's just what groups are made for. In your scenario the chunk of space
> would count only once. Some hopefully better explanation can be found at
Ohh, so the group is a union of the chunks in the members, not a sum?
So if you set an exclusive limit on the group, that would count
everything shared between 1, 2, 3 once, and not count any shared with Z?
In other words, --exclusive excludes space shared with things outside
the group, not within it?
> http://sensille.com/qgroups.pdf
>
> Have you already played with the patchset?
Not yet; I just found it today from the new thread on the subject, and
look forward to playing with it tonight. I was wondering what revision
the patches are based on, and are they in a public git repo?
next prev parent reply other threads:[~2011-11-21 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 8:21 [RFC] Subvolume Quota on-disk structures and configuration Arne Jansen
2011-08-24 7:26 ` Yeh
2011-08-24 7:53 ` Arne Jansen
2011-11-21 16:06 ` Phillip Susi
2011-11-21 17:20 ` Arne Jansen
2011-11-21 18:29 ` Phillip Susi [this message]
[not found] ` <4ECA9DBF.40104@gmx.net>
2011-11-21 20:15 ` Arne Jansen
2011-11-22 15:04 ` Phillip Susi
2011-11-22 15:07 ` Hugo Mills
2011-11-26 4:14 ` Phillip Susi
2011-12-01 9:15 ` Arne Jansen
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=4ECA9892.9070801@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sensille@gmx.net \
/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.