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
Kernel crash using BTRFS and KernelMemory with 1.10 #20080
Comments
Could be we need to up the minimum. |
Sorry, won't be able to experiment; had to hard reset server after freeze resulting in really bad data loss. |
This is a kernel bug which should be reported upstream. Raising the memory limit shouldn't be needed, but we can do it if that has become a requirement. |
Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=112101 |
Add the 'area/storage/btrfs' label to this. |
Hi, I've had the same problem (OOM and "kernel BUG at extent_io.c" ) with larger containers (16MB RAM). So raising the minimum mem limit won't solve this issue.
|
Let me close this ticket for now, as it looks like it went stale. |
Description of problem:
docker version
:docker info
:uname -a
:Environment details (AWS, VirtualBox, physical, etc.):
Physical.
How reproducible:
Steps to Reproduce:
Actual Results:
Crash and data loss
Expected Results:
No crash
Additional info:
Had no problems with 1.9.1.
You can see all /containers/create request data over at https://github.com/nfnty/dockerfiles/blob/master/containers.yaml
The text was updated successfully, but these errors were encountered: