Thanks everyone for the answers! On Wed, Jun 13, 2018 at 2:40 AM, Carlos Maiolino <cmaiolino@xxxxxxxxxx> wrote: > The symlink's project id, will always be related to the project id of its parent > directory. > > At the end, Project quota, is a way to create a directory tree based quota, > where all inodes corresponding to a single project id, should be under the same > subtree. If you are creating a new subtree, under an already existing project > id, IMHO, the right approach would be to remove the project id from the old > directory tree, and add it to the new tree, and use user/group quotas for any > quota accounting that should be done filesystem-wide (instead of directory tree > wise). It's a bit weird though that a symlink can inherit project ID from its parent directory, but then cannot get rid of it :) And thus doesn't allow to completely remove the project ID from the directory tree it's in. -- Ilya Pronin -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
