-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
More inodes needed #1443
Comments
I guess this is the mkfs line here:
the -i 8192 option is used, lowering this to -i 4096 or even lower would increase the number of inodes, I believe. |
I don't see any issue with changing the partition to have more inodes. Could you submit a PR making this change in minikube-automount? The CI will build the iso then you can test the iso w/ your workload using the CI build by running |
That's pretty cool. I'm currently building locally, but it takes a long time to build an entire Linux distribution! |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Could be either, depending on view
Minikube version (use
minikube version
):v0.18.0
Environment:
What happened:
Ran out of inodes.
What you expected to happen:
Default minikube environment would have enough inodes to run a replica of a good sized production environment
How to reproduce it (as minimally and precisely as possible):
Build a good number of docker images.
Anything else do we need to know:
See #1380 for a better long term solution and more background information, but in the interim, just formatting the partition with more inodes could help a lot. We could format with mkfs.ext4 -N 20000000; a better idea might be just to choose a better inode ratio, perhaps mkfs.ext4 -T news.
The text was updated successfully, but these errors were encountered: