TheSkaz Posted April 5, 2022 Share Posted April 5, 2022 I suspect this is a simple mistake on my end. my docker containers have filled up disk 1 i guess... but the appdata folder is set to "most-free" on allocation and none of the other disks will pick up. what did I screw up? backup-diagnostics-20220404-2058.zip Quote Link to comment
itimpi Posted April 5, 2022 Share Posted April 5, 2022 Do any of your docker containers refer to disk1 explicitly in their mappings? It should always be to /mnt/user/appdata/ Quote Link to comment
TheSkaz Posted April 5, 2022 Author Share Posted April 5, 2022 will double check, but I believe they do not explicitly connect to disk1 Quote Link to comment
Gragorg Posted April 5, 2022 Share Posted April 5, 2022 Verify your split level for the share that won’t spill over. Quote Link to comment
TheSkaz Posted April 5, 2022 Author Share Posted April 5, 2022 ok, I think I found it. the afffected folder is in system: root@Backup:/mnt/disk1/system/docker/docker/overlay2/0acecd8a19f448a03515b6e4e52fc21ee3a13e8dd295fc16949193dbe712b657# du -hc --max-depth=1 175G ./diff 0 ./work 175G ./merged 349G . 349G total and system's split level is "automatically split top level as required". I have changed it, is there a way to either: 1. find the docker and delete and redownload so its redistributed 2. have the system folder level out 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.