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

/var/vcap/store should not have 5% root reservation #112

Closed
CAFxX opened this issue Dec 8, 2016 · 2 comments
Closed

/var/vcap/store should not have 5% root reservation #112

CAFxX opened this issue Dec 8, 2016 · 2 comments
Labels

Comments

@CAFxX
Copy link

CAFxX commented Dec 8, 2016

Currently all filesystems are created with the default 5% disk space reservation for privileged processes. While this make sense for root filesystems, it's hard to justify for volumes that are normally only written to by non-root users (vcap), especially since it's not uncommon (at least in our experience) to have very large volumes (and, therefore, quite big amounts of unusable disk space)

I think it should be safe to use -m 0 on /var/vcap/store and /var/vcap/data, but if that's deemed too risky (why?) I would at least suggest lowering the reservation to some smaller value.

@cppforlife
Copy link
Contributor

@CAFxX i think it makes to be removed for persistent disk. for ephemeral storage it becomes a bit interesting since we have /var/vcap/data/root_log (bind mount from /var/log) placed there and it's written by auditd and rsyslog. not sure if they would be affected in a negative way. wdyt?

@CAFxX
Copy link
Author

CAFxX commented Dec 8, 2016

@cppforlife right, I forgot about that. Then yes, just /var/vcap/store.

@CAFxX CAFxX changed the title /var/vcap/store and /var/vcap/data should not have 5% root reservation /var/vcap/store should not have 5% root reservation Dec 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants