From: Jan Schmidt <list.btrfs@jan-o-sch.net>
To: Daniel Pocock <daniel@pocock.com.au>
Cc: cwillu <cwillu@cwillu.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-tools in Debian squeeze-backports?
Date: Wed, 04 Jan 2012 19:05:04 +0100 [thread overview]
Message-ID: <4F0494D0.2060607@jan-o-sch.net> (raw)
In-Reply-To: <4F01C6DC.3040609@pocock.com.au>
On 02.01.2012 16:01, Daniel Pocock wrote:
> One thing I've already noticed in 2.6.39 (and both versions of the
> tools) is that df results are misleading. E.g. if I run regular df (not
> btrfs fi df), I am seeing the same amount of available space for all
> filesystems. Is there currently a way to see space used by each
> subvolume and snapshot and which kernel and tools versions might be needed?
If you're interested (and brave), you might give the subvolume quota
patches a try. Arne sent them last October, subject
[PATCH v0 00/18] btfs: Subvolume Quota Groups
Be warned that this is a v0 patch, it's not been tested too much and
will very likely be reworked in the future. But that kind of
functionality will hopefully be added to btrfs, consequently.
-Jan
prev parent reply other threads:[~2012-01-04 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 14:29 btrfs-tools in Debian squeeze-backports? Daniel Pocock
2012-01-02 14:43 ` Hugo Mills
2012-01-02 14:55 ` cwillu
2012-01-02 15:01 ` Daniel Pocock
2012-01-02 15:14 ` Hugo Mills
2012-01-02 16:25 ` (renamed thread) btrfs metrics Daniel Pocock
2012-01-02 16:39 ` Hugo Mills
2012-01-04 11:48 ` Daniel Pocock
2012-01-04 18:46 ` Kok, Auke-jan H
2012-01-05 10:09 ` Daniel Pocock
2015-08-30 12:31 ` (renamed thread) btrfs metrics, free space reporting Daniel Pocock
2015-08-31 2:03 ` Qu Wenruo
2012-01-04 18:05 ` Jan Schmidt [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=4F0494D0.2060607@jan-o-sch.net \
--to=list.btrfs@jan-o-sch.net \
--cc=cwillu@cwillu.com \
--cc=daniel@pocock.com.au \
--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 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).