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.

Sign up for GitHub

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

Jump to bottom

quota: possible incorrect disk quota calculation on custom workspace paths #147

Open
mvidalgarcia opened this issue Oct 15, 2021 · 0 comments
Open

quota: possible incorrect disk quota calculation on custom workspace paths #147

mvidalgarcia opened this issue Oct 15, 2021 · 0 comments
Labels
priority/longterm size/l

Comments

@mvidalgarcia
Copy link
Member

If a user specifies a root_path different from the default one, they can bypass the disk quota limits. What is more, I guess initially the workflows would count for the disk quota as expected, but once the cronjob gets triggered, it would deduct those custom workspaces sizes. I haven't checked it deeply, writing from memory.

Just to take it into account, we might want to create an issue out of this to investigate it further.

Originally posted by @mvidalgarcia in #146 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/longterm size/l
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mvidalgarcia