We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am launching tokumx inside a docker container.
Very weird, as soon as I try to write to database, it throws the error "no space left".
But there are 37GB of free space.
How is it possible? Could it be that it throws that error based on percentage of free space instead of real free disk space?
The text was updated successfully, but these errors were encountered:
That is a possibility yes
Sent from my iPhone
On Jul 6, 2015, at 1:54 PM, Giovanni Gaglione [email protected] wrote: I am launching tokumx inside a docker container. Very weird, as soon as I try to write to database, it throws the error "no space left". But there are 37GB of free space. How is it possible? Could it be that it throws that error based on percentage of free space instead of real free disk space? — Reply to this email directly or view it on GitHub.
On Jul 6, 2015, at 1:54 PM, Giovanni Gaglione [email protected] wrote:
— Reply to this email directly or view it on GitHub.
Sorry, something went wrong.
This may be helpful regarding the percentage free space, http://docs.tokutek.com/tokumx/tokumx-server-parameters.html#tokumx-new-server-parameters-fsRedzone.
Please post these questions directly to our user group, https://groups.google.com/forum/#!forum/tokumx-user.
Joe
No branches or pull requests
I am launching tokumx inside a docker container.
Very weird, as soon as I try to write to database, it throws the error "no space left".
But there are 37GB of free space.
How is it possible? Could it be that it throws that error based on percentage of free space instead of real free disk space?
The text was updated successfully, but these errors were encountered: