June 12, 201610 yr Not sure what I am doing wrong Common Problem plugin has flagged my docker being 88% full but from the settings I thought everything was being stored in shared location on another my network. /downloads /mnt/disks/192.168.1.3_Downloads/ /watch /mnt/disks/192.168.1.3_Downloads/ /config /mnt/disk1/appdata/transmission/ Docker image is 10gb and I could increase the size but rather figure out why its filling up.
June 12, 201610 yr Author Index of /mnt/disks/192.168.1.3_Downloads/complete Index of /mnt/disks/192.168.1.3_Downloads/incomplete Looking at that it looks right to me but might be configured wrong within the settings. Manually searching the directories everything looks where its meant to be. Plex library is very big but cant image almost 10gb of metadata?
June 12, 201610 yr Index of /mnt/disks/192.168.1.3_Downloads/complete Index of /mnt/disks/192.168.1.3_Downloads/incomplete Looking at that it looks right to me but might be configured wrong within the settings. Manually searching the directories everything looks where its meant to be. Plex library is very big but cant image almost 10gb of metadata? yeah, but within the settings for you d/l client, you've got to tell it to store the incompletes within /downloads/incomplete, and the completes to /downloads/complete. If you're telling the dl client to store them within /mnt/disks/192.... then it'll be storing within the docker image.
June 12, 201610 yr Yes remember the docker translates: /downloads/incomplete => /mnt/disks/192.168.1.3_Downloads/incomplete if you tell the program in the docker to use the /mnt/disks/192.168.1.3_Downloads/incomplete - that is gonna get stored INSIDE the docker container thus increasing your docker.img useage so tell your docker program to use the /downloads/whatever paths instead and you will be fine Myk
June 12, 201610 yr Beyond that, for most use cases, a 10 gig image file (LT default) is actually rather small. Most people have ~20gig.
June 12, 201610 yr Community Expert I think what we are missing is possibly you are using unAssigned Devices to create a share that points to another computer on the network. If this is not what you are doing then I don't understand your volume mappings. edit - probably I was the only one to miss it ... but from the settings I thought everything was being stored in shared location on another my network...
June 12, 201610 yr I think what we are missing is possibly you are using unAssigned Devices to create a share that points to another computer on the network. If this is not what you are doing then I don't understand your volume mappings. BINGO! very good catch. Saw that, and it never really clicked in. If you're on 6.2, then those mappings in the template need to be mapped using one of the slave modes (rw:slave / ro:slave) If you're on 6.1 then you need to stop / restart the entire docker service for it to recognize those mappings. Failure to do this may result in the files being stored within the image even though everything else looks ok.
June 12, 201610 yr Author Yes exactly right, sorry should of mentioned using Unassigned Devices to use network share as TOWER only has a single 120gb SSD no cache or parity and the mounts point to my RIG1 in my sig. Looking at the dockers I have I think the culprit is sabnzbd as tranmission doesnt actually have a incompete folder. Attached some screenshots and docker have been restarted but something isnt still quite right.... Both machines are running 6.1.9 and only RIG2 has dockers installed.
June 12, 201610 yr Screenshots look ok. But, nothing is going to get that space back (beyond possibly deleting the logs), because if something went into the image, its pretty much there permanently unless you nuke the image and re-add the apps via CA's previous apps section. Either increase the image size, or check out this possibility: http://lime-technology.com/forum/index.php?topic=40937.msg475225#msg475225
June 12, 201610 yr Okay I will ask the obvious question... why is Rig 2 running the download process and saving across to Rig1? Rig1 look capable of handling that whole process.
June 12, 201610 yr Author Well I can up the image size to 20gb but wanted to understand why it got so full so quick. Only thing is the downloads. I am going to look at CP too but im hoping I can just manually find whats take the space and move it. @interwebtech RIG2 was meant to purely for PLEX but then I got into trying other dockers, RIG1 was originally version 5 until a few weeks ago. Might be easier to remove all the dockers to RIG1 with the exception of PLEX. Long week at work so will have to see how much time I get.. Thanks everyone for the help and replies. Just read http://lime-technology.com/forum/index.php?action=post;quote=432000;topic=45249.0;last_msg=475237 Could be CP logs. So did what it says and no longer getting error but how do I manually check docker.img usage and to increase the size to 20gb do you do it in docker settings and hit save or do you have to create a whole new image?
June 12, 201610 yr If you want, delete the docker.img completely then reinstall your docker containers but don't start any of them. Note how large each one is and how much space is used in total. Then start the containers and keep an eye on rapid growth and try to see what is actually going on for each docker app.
June 12, 201610 yr Author Think its looking better Total devices 1 FS bytes used 6.13GiB devid 1 size 20.00GiB used 9.04GiB path /dev/loop0 btrfs-progs v4.1.2 Increased to 20gb and think it was CP logs that were huge as a recently added my old library in there which was around 400 SD movies and wanted it to go look for the same but in min 720p. Not sure how I am going to manage the dupliacates but I will cross that bridge later.
Archived
This topic is now archived and is closed to further replies.