From: Arne Jansen <sensille@gmx.net>
To: Tomasz Chmielewski <tch@virtall.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs quota examples?
Date: Mon, 10 Jun 2013 09:41:39 +0200 [thread overview]
Message-ID: <51B58333.3050901@gmx.net> (raw)
In-Reply-To: <20130610152127.38fb8a50@virtall.com>
On 10.06.2013 08:21, Tomasz Chmielewski wrote:
> I'm trying to use btrfs quotas, but I'm unable to find reliable
> documentation on its usage.
>
> Let's start with an empty subvolume:
>
> - assign 200 MB space to it:
>
> # btrfs qgroup limit 200m /mnt/btrfs-backup/tester/
>
>
> - see the usage:
>
> # btrfs qgroup show /mnt/btrfs-backup/tester/
> 0/803 0 0
>
>
> - let's add a 100 MB file:
>
> # dd if=/dev/urandom of=bigfile bs=1M count=100
>
>
> - sync the FS to make sure quota is updated:
>
> # btrfs filesystem
> sync /mnt/btrfs-backup/ FSSync '/mnt/btrfs-backup/'
>
>
> - see current quota usage:
>
> # btrfs qgroup show /mnt/btrfs-backup/backuppc/tester/
> 0/803 104882176 104882176
>
>
> Now, my questions:
>
> - what do both 104882176 104882176 numbers represent?
The first number represents the amount of data in that subvolume,
regardless whether that data is shared with other subvolumes or
not.
The second number shows the amount of data that is unique to this
subvolume and not shared with others, i.e. the amount of space
that will get freed if you delete this subvolume.
For how this extends to quota groups see http://sensille.com/qgroups.pdf
>
> - how can I verify the quota assigned to any given subvolume? I've assigned 200 MB, but how can I verify that number?
The original patch set didn't include commands for that, but I
think I've seen patches for it on the mailing list, though I
can't find them right now.
-Arne
>
>
next prev parent reply other threads:[~2013-06-10 7:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 6:21 btrfs quota examples? Tomasz Chmielewski
2013-06-10 7:41 ` Arne Jansen [this message]
2013-06-10 7:47 ` Tomasz Chmielewski
2013-06-10 9:24 ` Wang Shilong
2013-07-29 8:05 ` Tomasz Chmielewski
2013-08-02 6:23 ` 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=51B58333.3050901@gmx.net \
--to=sensille@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=tch@virtall.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).