From: Anand Jain <Anand.Jain@oracle.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>,
Alex Lyakas <alex.btrfs@zadarastorage.com>
Cc: Wang Shilong <wangshilong1991@gmail.com>,
"dsterba@suse.cz Sterba" <dsterba@suse.cz>,
"linux-btrfs@vger.kernel.org FILE SYSTEM list:BTRFS"
<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] btrfs-progs: calculate disk space that a subvol could free
Date: Fri, 29 Nov 2013 09:57:09 +0800 [thread overview]
Message-ID: <5297F475.9070009@oracle.com> (raw)
In-Reply-To: <5297EF3F.4030400@cn.fujitsu.com>
> If so, i don't think this should be implemented in user space, Btrfs quota
> implement such function in kernel space, but it also face a problem that
> deleting a subvolume will break space accounting(because subvolume deletion
> won't iterate the whole fs tree).
Hi Alex, Wang.
Thanks for comments, as Wang suggested before, I am working on
the qgroups to handle our user space requisites here. I will be
sending out review patch soon. pls stay tuned.
Thanks, Anand
next prev parent reply other threads:[~2013-11-29 1:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 16:45 [PATCH] btrfs-progs: calculate disk space that a subvol could free Anand Jain
2013-09-27 19:10 ` Zach Brown
2013-09-28 17:19 ` Anand Jain
2013-09-29 15:02 ` Anand Jain
2013-10-01 13:25 ` David Sterba
2013-09-29 15:15 ` [PATCH V2] btrfs-progs: device add should check existing FS before adding Anand Jain
2013-09-29 15:26 ` Anand Jain
2013-09-29 15:25 ` [PATCH v2] btrfs-progs: calculate disk space that a subvol could free Anand Jain
2013-10-01 13:39 ` David Sterba
2013-10-01 14:05 ` Wang Shilong
2013-10-07 2:47 ` Anand Jain
2013-10-07 3:01 ` Wang Shilong
2013-10-07 3:22 ` Anand Jain
2013-10-08 16:49 ` David Sterba
2013-10-09 14:17 ` Wang Shilong
2013-10-10 3:35 ` Anand Jain
2013-10-10 3:33 ` Wang Shilong
2013-11-28 17:39 ` Alex Lyakas
2013-11-29 1:34 ` Wang Shilong
2013-11-29 1:57 ` Anand Jain [this message]
2013-10-09 8:03 ` Anand Jain
2013-10-09 8:35 ` Wang Shilong
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=5297F475.9070009@oracle.com \
--to=anand.jain@oracle.com \
--cc=alex.btrfs@zadarastorage.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@gmail.com \
--cc=wangsl.fnst@cn.fujitsu.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).