unRaide Posted January 17 Share Posted January 17 Hi, I'm getting this error filling up my logs which caused my server to stop responding earlier today requiring a reboot. After doing some search it seems like this error is usually caused by one of the shares exceeding it's minimum free space however looking through my shares I'm not seeing one like this? unraider-diagnostics-20240116-2323.zip Quote Link to comment
itimpi Posted January 17 Share Posted January 17 That message does not explain why the system would stop responding. It means that the cache has fallen below the minimum free space value allowed to write a new file to the cache, so the file will be written directly to the array instead. You have 100GB set as the minimum free for the cache so that is the value probably triggering it. I see that you have macvlan networking enabled for docker, but have not disabled bridging on eth0 as is recommended in the Unraid release notes to get maximum stability when using macvlan. Any reason for this? Quote Link to comment
unRaide Posted January 18 Author Share Posted January 18 (edited) On 1/17/2024 at 12:22 AM, itimpi said: That message does not explain why the system would stop responding. I misspoke somewhat, the webui wouldn’t load but my dockers and VMs were still accessible. On 1/17/2024 at 12:22 AM, itimpi said: It means that the cache has fallen below the minimum free space value allowed to write a new file to the cache, so the file will be written directly to the array instead. You have 100GB set as the minimum free for the cache so that is the value probably triggering it. I had a hard time finding this setting initially, but I believe it’s the one in the screenshot below , which currently looks to have a minimum free setting of 100 kB vs 100 GB - is the wrong setting? Additionally, I’m not sure how to change this value, perhaps I need to first stop the array? On 1/17/2024 at 12:22 AM, itimpi said: I see that you have macvlan networking enabled for docker, but have not disabled bridging on eth0 as is recommended in the Unraid release notes to get maximum stability when using macvlan. Any reason for this? No reason really – reading through the release notes iIt felt like this was an optional step but I’ll go back and reread it 😅. Edited January 18 by unRaide Quote Link to comment
Solution JorgeB Posted January 18 Solution Share Posted January 18 shfs: share cache full means that a share that is using cache is hitting the share floor, this is not the pool floor, when the pool floor is hit it's logged as: shfs: cache disk full 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.