May 7, 20251 yr I've gotten this error this morning with the Fix Problems plugin "Rootfs file is getting full (currently 98 % used)Possibly an application is storing excessive amount of data in /tmp." the only thing I know of that is in /tmp is a plex ram disk (which I don't remember how I setup, which isn't helping me diagnose the issue) but I would have set that probably 8-9 months ago and haven't had any issues since. Could anyone help with diagnose what could be causing this issue? widow-diagnostics-20250507-1243.zip Edited May 7, 20251 yr by widowshyper
May 7, 20251 yr Author 2 hours ago, trurl said: Post docker run for plex docker run -d --name='plex' --net='host' --cpuset-cpus='2,4,6,8,10,12,13,14,15,3,5,7,9,11' --pids-limit 2048 -e TZ="Australia/Hobart" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Widow" -e HOST_CONTAINERNAME="plex" -e 'VERSION'='docker' -e 'PLEX_CLAIM'='' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-1bddcbfb-3677-ed45-31e2-3a15a7134ae2' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-logo.png' -v '/mnt/user/data/':'/PlexVault':'rw' -v '/mnt/cache/transcode/':'/transcode':'rw' -v '/mnt/remotes/WINSVR_TheVault/Seeding/':'/RemoteJBOD':'ro,slave' -v '/mnt/cache/appdata/plex/':'/config':'rw' --device='/dev/dri' --runtime=nvidia 'lscr.io/linuxserver/plex' a918a8cb2053f03ef728f99fd1961a5ad70aca33b3aa680ad137ca7f35804983 The command finished successfully!
May 7, 20251 yr Community Expert No mapping to anything in rootfs there. No "ramdisk" in the mappings. Even your transcodes are going to cache. Assuming you have the plex application transcoding to that container path /transcode. If you haven't set that I think it transcodes into appdata, and if you have set it to something other than /transcode, such as /Transcode, that would be a path inside docker.img However, a likely cause of filling rootfs is indeed a container with a mapping to a host path that isn't actual mounted storage. Mounted storage is user shares, disks, pools, unassigned devices or remotes. What other containers do you have?
May 9, 20251 yr Author On 5/8/2025 at 2:11 AM, trurl said: No mapping to anything in rootfs there. No "ramdisk" in the mappings. Even your transcodes are going to cache. Assuming you have the plex application transcoding to that container path /transcode. If you haven't set that I think it transcodes into appdata, and if you have set it to something other than /transcode, such as /Transcode, that would be a path inside docker.img However, a likely cause of filling rootfs is indeed a container with a mapping to a host path that isn't actual mounted storage. Mounted storage is user shares, disks, pools, unassigned devices or remotes. What other containers do you have? I did have a Plex RAM Disk setup and I'm guessing that's what was causing my issues, since my rootfs has filled back up since I changed my transcode directory to my cache ssd. Not sure why it's suddenly filling up since I setup the ram disk probably 8-9 months ago.
May 9, 20251 yr Community Expert I don't see anything in your plex template that should write to rootfs. Maybe some other container?
May 9, 20251 yr Author 16 minutes ago, trurl said: What do you get from command line with this? df -h / and this? ls / I get this, It's been locked at 98% since I removed the ram disk. This was my original ram disk config inside my plex container Name: Transcode Container Path: /transcode Host Path: /tmp/PlexRamDisk Default Value: /tmp/PlexRamDisk Access Mode: Read/Write Display: Always Required: Yes Edited May 9, 20251 yr by widowshyper
May 9, 20251 yr Community Expert Solution 5 minutes ago, widowshyper said: It's been locked at 98% since I removed the ram disk. Reboot
May 11, 20251 yr Author ended up just having to swap my transcode directory to my cache ssd. unsure of why my ram disk was filling up and then not clearing itself out and was unable to diagnose why. Most likely a config issue on my end with how I setup the ram disk.
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.