Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FEATURE: BTRFS Subvolume quota #1

Open
Tux12Fun opened this issue Oct 17, 2017 · 1 comment
Open

FEATURE: BTRFS Subvolume quota #1

Tux12Fun opened this issue Oct 17, 2017 · 1 comment

Comments

@Tux12Fun
Copy link

It would be nice to have a Quota Support for the Subvolume.
Unfortunately I haven't written something in Python, so I'm unable
to code it on my one. I hope this contribution is usefull.

The commands would be:

btrfs quota enable /path/to/subvolume
btrfs qgroup limit 4m /path/to/subvolume

Maybe we could define it like this:

 btrfs__subvolumes:         {
    "/data/mariadb/logs/mariadb":
    dir_owner=mysql
    dir_group=mysql
    state=present,
    "/data/mariadb/data/mariadb":
    dir_owner=mysql
    dir_group=mysql
    state=present,
    "/data/mariadb/data/test1":
    dir_owner=xyz
    dir_group=abc
    quota="4M"
    state=present
 }

A other Question:
What is the reason for:

btrfs__subvolumes_host_group

and

btrfs__subvolumes_host:

I've never used this Variables.

@ypid
Copy link
Member

ypid commented Oct 19, 2017

Hi

Thanks for your input. I will consider it when I need quotas for Btrfs but maybe don’t expect this too soon. I can not tell you an ETA currently.

btrfs__subvolumes_host_group vs. btrfs__subvolumes_host

You are right. It is a bit uncommon outside of DebOps currently. Refer to Inventory level scoped variables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants