From: Arne Jansen <sensille@gmx.net>
To: miaox@cn.fujitsu.com
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
wangshilong <wangsl-fnst@cn.fujitsu.com>
Subject: Re: About btrfs qgroup import/export command
Date: Wed, 19 Dec 2012 12:40:25 +0100 [thread overview]
Message-ID: <50D1A7A9.9010300@gmx.net> (raw)
In-Reply-To: <50D1A430.607@cn.fujitsu.com>
On 19.12.2012 12:25, Miao Xie wrote:
> Hi, everyone.
>
> As we know, there is no backup function for qgroup. when the problem
> occurs, the users must recover qgroup configuration manually, it is not
> convenient. And besides that, some users might want to import an existed
> qgroup configuration into a new filesystem. Btrfs does not have such a
> function,it can only be done manually.
>
> So we want to implement btrfs qgroup import/export commands.
> 1)'btrfs qgroup export' commands will export qgroup tree
> into a user's specified file.(stdout by default)
>
> 2)user may modify the configuration file firstly and then
> import it into the filesystem.(by 'btrfs qgroup import' command)
>
> The file may be formated as the following:
>
> Qgroupid is_compressed is_exclusive limited_size parent
> ----------------------------------------------------------------------
> 0/1 0 0 10G 1/0
> 1/0 1 1 20G ---
>
> If 'is_exclusive' is set, 'limited_size' corresponds to max exlusive size,
> else max referenced size. Here 'parent' exclude ancestral qgroups.
>
> Is there any comment about this idea?
The configuration only really makes sense in combination with the existing
subvolumes. Even if the target has subvolumes under the same name, they
might have different internal IDs. So it might make more sense to address
the level 0 qgroups by name.
Also it might be misleading to apply a configuration to an existing fs, as
it currently is not possible get a correct accounting if the fs is not
empty. Rescan is not yet implemented.
So instead of just saving and restoring the qgroup config, it might make
more sense to create a new filesystem including all subvolumes and quota
config from a config file.
But, I'm not completely convinced that this is a features that is needed
frequently. If I want a standard deployment, I simple write a script that
creates the fs + subvol + quota.
-Arne
>
> Thanks
> Miao
>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2012-12-19 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50D1632E.6010801@cn.fujitsu.com>
2012-12-19 11:25 ` About btrfs qgroup import/export command Miao Xie
2012-12-19 11:40 ` Arne Jansen [this message]
2012-12-20 3:17 ` Miao Xie
2013-01-09 10:17 ` Miao Xie
2013-01-09 12:18 ` 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=50D1A7A9.9010300@gmx.net \
--to=sensille@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.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 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.