Jump to content

Rootfs is getting filled error


Recommended Posts

I will make a couple of suggestions.  First, this problem is often caused by a VM or a Docker which is not writing files to a physical device.  Thus, they end up in RAM which causes the rootfs full warning. 

 

In the case of a VM, it could be an issue with a default mapping of a application running on the VM.

 

With Dockers, the problem is often caused when the mapping is (1) changed from the default or (2) is manually added when it is being setup. 

 

Couple of ways to find it.

 

1---  Look at all of the mappings and made sure that they are actually going to a physical device.  Normally with Unraid, all of these are in the   /mnt  directory.  However, you can create a file system under /mnt very easily-- usually a typo. These will end up in RAM...   Normally, the file listing for the  /mnt  directory should look similar to this:

image.png.fcaf61ff29210b289354a80232ad7455.png

If you find something else there, it should be considered very suspect.  (There is one more entry that is often found here that is generated by the Unassigned Devices plugin and I believe it is named disks.)

 

2--- Stop each VM or Docker from starting (one at a time) and reboot.  Then wait to see if the error message reappears.   IF it doesn't, you have found the problem child.

 

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...