March 26, 20251 yr I started getting an error that rootfs is getting full. It is currently at 93%. Everything was running great for quite a while, it seemed. Then, this error started occurring. Any assistance would be greatly appreciated. unraid-diagnostics-20250326-1826.zip
March 26, 20251 yr Community Expert Had another thread about this earlier. Rather than type all that again I will just link my post explaining what usually causes this:
March 29, 20251 yr Author I verified the share paths; I believe they are correct. I haven't changed anything on this server in a very long time, and this is a new issue for me. Could it be Mover-related? I believe I received an update recently that required me to change Mover plugins. After this, I had to set the Mover settings up again from new. It is possible I could have messed that up. Like I said, it has been quite a while since I built this server.
March 29, 20251 yr Community Expert The new Mover Tuner plugin currently has a bug that generates ungodly amount of logs and fills the rootfs. Might want to get rid of that until they sort it out.
April 12, 20251 yr On 3/29/2025 at 3:44 PM, Kilrah said: The new Mover Tuner plugin currently has a bug that generates ungodly amount of logs and fills the rootfs. Might want to get rid of that until they sort it out. That hint was a life-saver in my case. Even with the latest version from 2025-04-05 and a 5 day log rotation, the default log folder at `/tmp/ca.mover.tuning` was 3.3G big (`du -h`) with single log files consuming 430M (`ls -lah`) I created a log folder in the array, in `/mnt/user/appdata/ca.mover.tuning`, and changed the Mover Tuner plugin settings to use that location instead.
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.