cagemaster Posted June 3, 2019 Share Posted June 3, 2019 Hi! Yesterday I downloaded a large file to my cache drive and when I woke up this morning my cache was full and Docker containers weren't accessible. I thought that was weird since the moved should have been invoked, and also the share holding the large file is set to "use cache drive: yes". I tried removing the large file but unraid didn't notice the change in disk space. I shut down the docker image and got this message. Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 655 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 827 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 655 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 891 Then checking Fix Common Problems i got this error: Unable to write to cacheDrive mounted read-only or completely full. Begin Investigation Unable to write to Docker ImageDocker Image either full or corrupted. Investigate I then tried to shut down the array, but the disks won't unmount. I did a diagnostics dump (attached). Any help would be appreciated! Thank you! mercury-diagnostics-20190603-0647.zip Quote Link to comment
Glassed Silver Posted June 3, 2019 Share Posted June 3, 2019 My first thought is that old snapshots are keeping the drive full maybe. Cache drives use btrfs and whilst I’m new to btrfs myself I believe I know enough to at least point into the direction. This page might help you: http://marc.merlins.org/perso/btrfs/post_2014-05-04_Fixing-Btrfs-Filesystem-Full-Problems.html Let me know if it works. Quote Link to comment
cagemaster Posted June 3, 2019 Author Share Posted June 3, 2019 As the drives did not unmount i force restared the server, now everything is working fine... I do not know what solved the problem and why it occured in the first place. A docker image scrub told me 0 errors. Quote Link to comment
Glassed Silver Posted June 3, 2019 Share Posted June 3, 2019 8 minutes ago, cagemaster said: As the drives did not unmount i force restared the server, now everything is working fine... I do not know what solved the problem and why it occured in the first place. A docker image scrub told me 0 errors. The docker file was fine, it was the cache drive’s filesystem requiring a scrub. Quote Link to comment
JorgeB Posted June 3, 2019 Share Posted June 3, 2019 Cache filesystem is fully allocated (and practically all used), but because it's fully allocated it will run out of space even before being fully used, see here for how to fix. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.