Scurz
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Scurz
-
-
1 minute ago, itimpi said:
I personally have no experience of using that script. Was that script run at a point when you were getting a report that the free space was low? That would be needed in case a particular container is writing working file internally to the image and later deleting them.
Yes, The script was run yesterday when my docker.img was full.
-
On 12/3/2023 at 4:29 AM, itimpi said:
If you get this then you almost certainly have at least one docker container with the volume mapper wrong/insufficient so that it is writing temporary files internally to the image file rather than to external storage on the Unraid host. The fact that you have an image file anywhere near that size suggests you increased it in the past to try and avoid such a problem - the default of 20GB is enough for the vast majority of people if they have all their docker containers correctly configured to not write internally to the image file.
You may find this video from SpaceInvader One of use in identifying the culprit(s)
Hi, I looked into the video, tough I'm still confused as to which container is taking up all that space;
Here's a paste of SpaceInvader's script result:https://pastebin.com/raw/DeTjKC1Z
Removing Orphaned Images:
https://pastebin.com/raw/jGdfLWAE
Does anything look out of the ordinary?
-
I am getting daily notifications that my docker.img is full though I am certain it is not;
My docker.img is an absurdly large 110GB
Here is a list of my containers and their sizes: https://pastebin.com/raw/VtYgHNABThis adds up to 56GB - Just over half... Where is the other 54GB??
-
2 minutes ago, itimpi said:
Try removing the Mover Tuning plugin. Been quite a few reports recently of it causing this sort of issue.
This seems to have worked - Thanks! -
I have a 2TB HDD cache "drivecache" that I use to reduce wear to my array. For some reason, The mover takes no action when it fills up, even when manually running it. I've ensured that all shares are Drivecache -> Array but the files seem to stay on the Drivecache?
I've attached diagnostics. Let me know if more info is required.
-
Just now, JorgeB said:
There are a lot of:
Jul 6 09:46:05 Paradigm move: move_object: //..f/... File exists Jul 6 09:46:05 Paradigm move: file: //..g/... Jul 6 09:46:05 Paradigm move: move_object: //..g/... File existsMover won't move files that already exist on destination.
Does that mean I can safely replace the cache disk without losing data? -
I'm trying to offload my cache disk so i can replace it but the mover refuses to work
It "runs" for ~5 sec and then immediately stops. There's still 197GB on my cache that I can't move. -
Title explains all. My cpu hovers between 85-100%
I have no idea how to fix this.
.png.a7141683273a09acdf427c7e317dd939.png)
.thumb.png.16ed5accfab903745f3451837b73c209.png)
.thumb.png.1261947838624b6e79e7453883e6281a.png)
-
Something really wrong went on during get_content
Post the ENTIRE contents of this message in the Community Applications Support ThreadOS: 6.12.0-rc3
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36
Language:No data was returned. It is probable that another browser session has rebooted your server. Reloading this browser tab will probably fix this error
-
On 4/3/2023 at 5:53 AM, JorgeB said:
If it's a one time thing you can ignore, if it keeps happening try limiting more the RAM for VMs and/or docker containers, the problem is usually not just about not enough RAM but more about fragmented RAM, alternatively a small swap file on disk might help, you can use the swapfile plugin:
I installed the sawpfile plugin and set it to 10G - yet it's still running out of memory?
Updated diagnostics attached
-
My 110GB Docker image is nearly full. Is this normal for how many containers I'm running?
"Container Size" results: https://pastebin.com/0dMrMtpm
Results from a script from Spaceinvader One: https://pastebin.com/5EDPV3XT
Results from docker log script: https://pastebin.com/BctLmrag
Nothing looks out of the ordinary to me but 110GB seems pretty high?
Let me know if any other info is required. -
I've been getting an out of memory error at least daily for the past week but can't seem to figure out the cause.
paradigm-diagnostics-20230402-0448.zipI've attatched my diagnostics. Can someone help me figure this out?
-
Update: I'm unable to create new shares to transfer over the data. It just takes me through the process and returns me to this page:
Should I restart the system? I'm worried it will wipe the files in my cache pool.
-
In an attempt to free up space on my unraid sheare, I set "Use cache pool: No".
Upon hitting "apply", I was greeted with "Share Deleted"
Through the file manager, I still see my data. Some in my cache pool and some in disk1 (my only disk)
UPDATE: I've restarted the system and the share seems to have returned properly. I will send a follow up if anything fails.
.png.a7141683273a09acdf427c7e317dd939.png)
.png.f7e2678db9b9362702601d2be85b084b.png)
.png.65ef9028c3d6e4cd9da4539215704317.png)
Docker Service failed to start.
in General Support
Posted
Not sure what caused this. Diagnostics are attached.
paradigm-diagnostics-20231216-1420.zip