Posted September 16, 20186 yr While checking the log to determine what was causing some drives to spin up, I saw an entry that mentioned "Warning: Rootfs file is getting full (currently 81 % used)". What causes this usually, and how can I prevent it? I'm attaching diagnostics file, thanks for your help! tower-diagnostics-20180916-0538.zip
September 16, 20186 yr Community Expert Difficult to say! Most likely cause is a misconfigured docker that is writing files to RAM. The thing to remember is that all files that are not under /mnt or /boot are in RAM.
September 16, 20186 yr Author Thanks, as far as I know I have all my data files under /mnt. I tried looking at the Diagnostics file but I don't know where to look... has someone else had this issue before?
September 16, 20186 yr Community Expert 5 hours ago, fersal said: as far as I know I have all my data files under /mnt Is this a new problem? Have you made any recent changes or additions to dockers? 10 hours ago, itimpi said: Most likely cause is a misconfigured docker that is writing files to RAM. The thing to remember is that all files that are not under /mnt or /boot are in RAM. This is the most usual cause of this problem. And /mnt isn't good enough actually. It must be an actual user share path, /mnt/user/... or an actual disk, /mnt/disk1/... or /mnt/cache/... for example. Just /mnt/somefolder will still be in RAM. And you can also get a folder in RAM if you try to use a path to an unmounted Unassigned Device.
September 17, 20186 yr Author 4 hours ago, trurl said: Is this a new problem? Have you made any recent changes or additions to dockers? This is the most usual cause of this problem. And /mnt isn't good enough actually. It must be an actual user share path, /mnt/user/... or an actual disk, /mnt/disk1/... or /mnt/cache/... for example. Just /mnt/somefolder will still be in RAM. And you can also get a folder in RAM if you try to use a path to an unmounted Unassigned Device. Actually no major hardware or software changes in the past year other than upgrade to 6.5.3. However maybe it's happened before because I don't look at the log file very often. The only docker is a Plex Media Server. And yes, all files are in user shares under /mnt/user/; I'll keep monitoring the log file to see of this happens again. If anyone else has any ideas please let me know, thanks! Edited September 17, 20186 yr by fersal
September 17, 20186 yr Author One thing that I did notice was that in the Docker volume mappings for Plex I have everything under /mnt/user/ except one entry that says: /transcode <--> /tmp Could this be causing this issue? Edited September 17, 20186 yr by fersal
September 17, 20186 yr Community Expert /tmp is in RAM but some people set it up that way on purpose so transcodes go to RAM. I guess it depends on how much RAM you have and how big transcodes are.
November 3, 20186 yr I just upgraded to 6.6.3 and installed FCP and ran a diagnostics. It is showing an error for me saying "Rootfs file is getting full (currently 99& used). Not sure why I am getting this now. I don't have docker enabled. Attaching my diagnostics.. storage-diagnostics-20181103-2354.zip
November 3, 20186 yr Community Expert Running unRaid 6.6.3 on 2G of memory is really pushing it. I know that LT's website does state that is the requirement, but realistically that is the bottom of the barrel requirement.
November 3, 20186 yr 1 hour ago, Squid said: Running unRaid 6.6.3 on 2G of memory is really pushing it. I know that LT's website does state that is the requirement, but realistically that is the bottom of the barrel requirement. Thanks for responding and checking my logs! How much should be the RAM then? Any recommendation? Edited November 3, 20186 yr by anindianforor
November 3, 20186 yr Community Expert 2 hours ago, anindianforor said: Thanks for responding and checking my logs! How much should be the RAM then? Any recommendation? TBH, even with no additional apps running, I'd say 4G is the functional minimum
August 8, 20213 yr On 11/3/2018 at 6:19 PM, Squid said: TBH, even with no additional apps running, I'd say 4G is the functional minimum Hello, I have posted my diagnostics for some assistance. Keep in mind this NAS is sort of a test NAS I created from old hardware and upgraded RAM and CPU to what the motherboard would support. Fix uncommon problems is reporting: Rootfs file is getting full (currently 92 % used) Is this cause of the RAM? unraidNAS-diagnostics-20210808-1202.zip
August 8, 20213 yr Community Expert You have 2GB of memory On 11/3/2018 at 6:19 PM, Squid said: I'd say 4G is the functional minimum
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.