knert88 Posted November 19, 2019 Share Posted November 19, 2019 Hi! Have been searcing this forum a while, to try and figure what´s wrong with my server - but no luck yet. My rootFS is slowly filling up with some data - have reinstalled some dockers, especially Plex, and checked the folder mappings. But after 2-3 days the rootFS is back to around 90%. Any tips on how to identify what´s writing to root? tower-diagnostics-20191119-1759.zip Quote Link to comment
John_M Posted November 19, 2019 Share Posted November 19, 2019 Well, it isn't your syslog that's growing out of control so it's probably worth checking those container mappings again. You could have misspelt one or got the case wrong. Suppose you have a user share called "Downloads" but your container mapping points to /mnt/user/downloads instead of /mnt/user/Downloads - that will write to the root FS instead of to disk. Quote Link to comment
knert88 Posted November 19, 2019 Author Share Posted November 19, 2019 15 minutes ago, John_M said: Well, it isn't your syslog that's growing out of control so it's probably worth checking those container mappings again. You could have misspelt one or got the case wrong. Suppose you have a user share called "Downloads" but your container mapping points to /mnt/user/downloads instead of /mnt/user/Downloads - that will write to the root FS instead of to disk. Yeah, I did this one more time, edited the mapping of each docker with the "drop-down" file-explorer, not typing the path´s manually. I have a feeling that there is something with the Plex docker that is misconfigured, but I´m having a hard time identifying what´s wrong. Quote Link to comment
John_M Posted November 19, 2019 Share Posted November 19, 2019 If you post your configuration or your docker run command someone might spot something that isn't quite right. Quote Link to comment
knert88 Posted November 19, 2019 Author Share Posted November 19, 2019 24 minutes ago, John_M said: If you post your configuration or your docker run command someone might spot something that isn't quite right. Here is a screenshot of my volume mappings pr. docker. Quote Link to comment
BRiT Posted November 19, 2019 Share Posted November 19, 2019 According to your diagnostic and "df", You do not have a cache disk, why are you using /mnt/cache/ in your mappings? Quote Link to comment
itimpi Posted November 19, 2019 Share Posted November 19, 2019 Just now, BRiT said: According to your diagnostic and "df", You do not have a cache disk, why are you using /mnt/cache/ in your mappings? That could definitely cause problems as without a cache disk /mnt/cache will be in RAM. Quote Link to comment
masorrell Posted September 22, 2021 Share Posted September 22, 2021 I'm assuming since there was no further replies, that was it... 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.