Squid Posted August 28, 2015 Share Posted August 28, 2015 Try moving the transcode directory into appdata Did the default directory change from the appdata directory to the docker.img? I've never had that directory set. What should I set it to? No. But its something that can be safely moved out of the img file. Its where plex stores its temporary files for transcoding. Normally I think its set within plex to be /transcode, but you can set it to be something like /config/plex/transcode (or however you've mapped the appdata share) Not saying that this is the problem, as its only used during transcodes, but maybe. So long as you've mapped the appdata correctly, then all the thousands of files that plex uses for its metadata should be stored outside the img Quote Link to comment
JimPhreak Posted August 28, 2015 Author Share Posted August 28, 2015 Try moving the transcode directory into appdata Did the default directory change from the appdata directory to the docker.img? I've never had that directory set. What should I set it to? No. But its something that can be safely moved out of the img file. Its where plex stores its temporary files for transcoding. Normally I think its set within plex to be /transcode, but you can set it to be something like /config/plex/transcode (or however you've mapped the appdata share) Not saying that this is the problem, as its only used during transcodes, but maybe. So long as you've mapped the appdata correctly, then all the thousands of files that plex uses for its metadata should be stored outside the img The transcoding directory is part of the problem because when I'm transcoding I see the docker.img used space going up quickly. Then when I stop playing the video that used space goes away as it's probably deleting that temp data. However it can't be the only issue because even with no data transcoding at all, my used spaced jumped from just over 3GB to just over 8GB in one day. Is there anyway to explore what's on the docker.img file? Quote Link to comment
Squid Posted August 28, 2015 Share Posted August 28, 2015 docker exec -it docker-name bash But it would have to be the meta data that's causing it to balloon like that. And if the mapping is right its outside the image Quote Link to comment
Squid Posted August 28, 2015 Share Posted August 28, 2015 Unless you've installed some extras for Plex that are causing it.... Quote Link to comment
JimPhreak Posted August 28, 2015 Author Share Posted August 28, 2015 docker exec -it docker-name bash But it would have to be the meta data that's causing it to balloon like that. And if the mapping is right its outside the image This is my config mapping. It's the same as it's been ever since I've had the Plex docker (months) and it's never changed. Yet all of a sudden this is a problem. Using that bash command, is there any easy way to view the size of each of the directories? If I do a ls -lah from the root, some of the directories show their size and some just have a number without any indication of the form of data measurment (KB, MB, GB, etc.). Unless you've installed some extras for Plex that are causing it.... I've installed no extras in Plex except for the RottenTomatoes metadata agent but I've had that from the beginning. Quote Link to comment
Squid Posted August 28, 2015 Share Posted August 28, 2015 Mobile so can't answer on off the top of my head. But, I looked again at your screen shots of your docker img. The one line did go up from 7 gig to 8.5 gig. However, the line stating the size / used remained constant at 20G / 13.04 gig. Not *quite* sure about the significance there, as BTRFS leverages COW, but I *think* its the second line that's the important one here. Never really investigated it that closely... Quote Link to comment
trurl Posted August 28, 2015 Share Posted August 28, 2015 docker exec -it docker-name bash But it would have to be the meta data that's causing it to balloon like that. And if the mapping is right its outside the image ... Using that bash command, is there any easy way to view the size of each of the directories? If I do a ls -lah from the root, some of the directories show their size and some just have a number without any indication of the form of data measurment (KB, MB, GB, etc.). The du Command Quote Link to comment
JimPhreak Posted August 28, 2015 Author Share Posted August 28, 2015 docker exec -it docker-name bash But it would have to be the meta data that's causing it to balloon like that. And if the mapping is right its outside the image ... Using that bash command, is there any easy way to view the size of each of the directories? If I do a ls -lah from the root, some of the directories show their size and some just have a number without any indication of the form of data measurment (KB, MB, GB, etc.). The du Command Thanks. Everything looks fine in there. Mobile so can't answer on off the top of my head. But, I looked again at your screen shots of your docker img. The one line did go up from 7 gig to 8.5 gig. However, the line stating the size / used remained constant at 20G / 13.04 gig. Not *quite* sure about the significance there, as BTRFS leverages COW, but I *think* its the second line that's the important one here. Never really investigated it that closely... The second line used space has gone up 6GB since yesterday. Yesterday when it crashed Yesterday after rebuild Today Quote Link to comment
JimPhreak Posted August 29, 2015 Author Share Posted August 29, 2015 Welp. I'm screwed. Gonna have to delete my docker.img again and start from scratch. Quote Link to comment
interwebtech Posted August 29, 2015 Share Posted August 29, 2015 my Plex docker mapping settings: /config => /mnt/user/appdata/plexmediaserver /transcode => /tmp the rest are pointers to media locations. for the /transcode setting to work you have to edit the server setting inside Plex advanced settings. Quote Link to comment
JimPhreak Posted August 29, 2015 Author Share Posted August 29, 2015 my Plex docker mapping settings: /config => /mnt/user/appdata/plexmediaserver /transcode => /tmp the rest are pointers to media locations. for the /transcode setting to work you have to edit the server setting inside Plex advanced settings. Why not just put the transcode directory inside the /mnt/user/appdata/plexmediaserver directory? Quote Link to comment
interwebtech Posted August 29, 2015 Share Posted August 29, 2015 my Plex docker mapping settings: /config => /mnt/user/appdata/plexmediaserver /transcode => /tmp the rest are pointers to media locations. for the /transcode setting to work you have to edit the server setting inside Plex advanced settings. Why not just put the transcode directory inside the /mnt/user/appdata/plexmediaserver directory? Because using that setting puts it in RAM. Even faster than the SSD where appdata is located Quote Link to comment
JimPhreak Posted August 29, 2015 Author Share Posted August 29, 2015 my Plex docker mapping settings: /config => /mnt/user/appdata/plexmediaserver /transcode => /tmp the rest are pointers to media locations. for the /transcode setting to work you have to edit the server setting inside Plex advanced settings. Why not just put the transcode directory inside the /mnt/user/appdata/plexmediaserver directory? Because using that setting puts it in RAM. Even faster than the SSD where appdata is located What's the most amount of transcodes you have going at once and how much RAM do you have dedicated to your server? I will often have 5-6 transcodes going simultaneously and have 12GB of RAM dedicated to my unRAID server. Quote Link to comment
interwebtech Posted August 29, 2015 Share Posted August 29, 2015 3 or 4 transcodes at max. I used to have 8GB and now have 16GB RAM. Worked fine either way. Quote Link to comment
trurl Posted August 29, 2015 Share Posted August 29, 2015 my Plex docker mapping settings: /config => /mnt/user/appdata/plexmediaserver /transcode => /tmp the rest are pointers to media locations. for the /transcode setting to work you have to edit the server setting inside Plex advanced settings. Why not just put the transcode directory inside the /mnt/user/appdata/plexmediaserver directory? You can do that, but you should check and make sure the plex advanced settings are putting the transcodes somewhere in some container volume. Quote Link to comment
JimPhreak Posted August 29, 2015 Author Share Posted August 29, 2015 After re-installing Plex with Linuxserver's contrainer (used to use Needo's) the transcoder directory is listed as such in the Plex server settings: \Library\Application Support\Plex Media Server\Cache\Transcode Quote Link to comment
JimPhreak Posted August 30, 2015 Author Share Posted August 30, 2015 I don't know what the heck to do at this point. My transcode folder is as stated in the above post but yet my docker.img looks like this now. Quote Link to comment
scottc Posted August 30, 2015 Share Posted August 30, 2015 Double check you do not have debug logging or anything like that enabled in plex, i know if you turn on debug logging it will eat up space quickly ( even faster with a large library ) Quote Link to comment
JimPhreak Posted August 30, 2015 Author Share Posted August 30, 2015 Double check you do not have debug logging or anything like that enabled in plex, i know if you turn on debug logging it will eat up space quickly ( even faster with a large library ) I do have that enabled but need it to be for PlexPy. I've had all my settings set exactly the same for months though so why would it start all of a sudden start saving outside the appdata folder? Quote Link to comment
scottc Posted August 30, 2015 Share Posted August 30, 2015 actually you are correct, logs are stored in the appdata folder and not in the container. These are the dockers you are running right? CP DelugeVPN Legacy ruTorrent Plex Media Server Plexpy Plex Requests Sonarr Subsonic I would go through the settings of any that download stuff ( CP, DelugeVPN, Legacy ruTorrent ) and double check the temp download folders are mapped correctly. I remember one the other day that had CP set to temp download to /something/Incomplete-Downloads ( i dont remember the exact structure ) and CP uses relative directories so it was download all stuff to the docker image then moving it out to the array and his docker.img was filling up. he changed the /something/Incomplete-Downloads to something/Incomplete-Downloads ( removing the first / ) and it solved his issue. Quote Link to comment
JimPhreak Posted August 30, 2015 Author Share Posted August 30, 2015 actually you are correct, logs are stored in the appdata folder and not in the container. These are the dockers you are running right? CP DelugeVPN Legacy ruTorrent Plex Media Server Plexpy Plex Requests Sonarr Subsonic I would go through the settings of any that download stuff ( CP, DelugeVPN, Legacy ruTorrent ) and double check the temp download folders are mapped correctly. I remember one the other day that had CP set to temp download to /something/Incomplete-Downloads ( i dont remember the exact structure ) and CP uses relative directories so it was download all stuff to the docker image then moving it out to the array and his docker.img was filling up. he changed the /something/Incomplete-Downloads to something/Incomplete-Downloads ( removing the first / ) and it solved his issue. CP and Sonarr don't actually download anything so I don't see how those are issues. I even looked in both their settings and there is no where to even set temp directories because they are just accessing NZBGet/Deluge/ruTorrent to do the downloads. I took some SS's of those downloader programs below but nothing stands out to me. Deluge NZBGet ruTorrent Quote Link to comment
Squid Posted August 30, 2015 Share Posted August 30, 2015 You should also post the volume mappings for each of those apps. Quote Link to comment
JimPhreak Posted August 30, 2015 Author Share Posted August 30, 2015 You should also post the volume mappings for each of those apps. Just did . Quote Link to comment
Squid Posted August 30, 2015 Share Posted August 30, 2015 Your category settings in NZBGet for Television and Movies is specifying a destination directory of /Series and /Movies But you haven't mounted them. Anything downloaded for this category winds up being moved into the docker.img Quote Link to comment
JimPhreak Posted August 30, 2015 Author Share Posted August 30, 2015 Your category settings in NZBGet for Television and Movies is specifying a destination directory of /Series and /Movies But you haven't mounted them. Anything downloaded for this category winds up being moved into the docker.img Doesn't the DestDir to the left of it mean it will be stored in DestDir /"whateverIset"? 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.