Hi guys, If a qgroup is created for a btrfs subvolume /some/path and limits are set and a new btrfs subvolume /some/path/bla is created it does not inherit the parent subvolume's /some/path qgroup and limits. The only way to achieve something similar is to create a common "parent" qgroup and assign both, the parent btrfs subvolume /some/path and the child subvolume /some/path/bla to this qgroup. This seems unintuitive and actually proves to be a problem. For example, when creating a container that uses a btrfs subvolume as storage backend and then allowing users to create additional subvolumes in another container they can easily escape the qgroup and its limits and even with the common qgroup nothing seems to prevent them from simply removing themselves from this qgroup. What is the proper way to deal with this case such that: a) the subvolume automatically gets the same qgroup as the parent b) cannot escape the qgroup
where b) is the more pressing concern. Thanks! Christian
signature.asc
Description: PGP signature
