Oct 19, 2016 14:25:37.979 [0x2b8514a00700] WARN - Low disk space: 7.65GB source file, 7.66GB capacity, 7.15GB available on /transcode
Oct 19, 2016 14:25:37.979 [0x2b8514a00700] WARN - TranscodeSession: inadequate disk space for transcode
Oct 19, 2016 14:25:37.979 [0x2b8514a00700] DEBUG - Streaming Resource: Terminated session 0x2b8510939ea0:vv7x6rl66d8opmjqhmxyiizfr with reason Not enough disk space to convert this item.
I get the above when I try to play a movie. Not really sure why. The transcode directory is using memory, which I have 15GB available… Never seen this before, thoughts? I am assuming I can just point it to local disk but I liked running it off of memory previously.
It states there is only 7.15G available on /transcode. What’s the size of that disk? 7.15G is not enough space for the transcoder on this source file.
@gbooker02 said:
It states there is only 7.15G available on /transcode. What’s the size of that disk? 7.15G is not enough space for the transcoder on this source file.
I am using a method to use RAM, which is 15GB available. This method is for unRAID (although it might be for others), Plex: Guide to Moving Transcoding to RAM - Docker Containers - Unraid
It has worked perfectly fine until today. And like I said, RAM is around 15GB free. If I move it to local SSD storage it works fine. I am fine with that, just not sure why out of the blue it stopped working.
So, you’re using a RAM disk which is portioning a part of the RAM to create a block storage device. The question still remains, what is the size of the filesystem containing /transcode? Depending on the exact technique used, it’ll have a capacity of the total RAM size at the absolute most. Most likely, given the detected capacity of 7.66GB, it is much smaller and doesn’t dynamically change. It has a finite size one way or another and the log line indicates that it had 7.15GB free and the estimate of the size required was 7.65GB. That’s why it didn’t start the transcoder.
@gbooker02 said:
So, you’re using a RAM disk which is portioning a part of the RAM to create a block storage device. The question still remains, what is the size of the filesystem containing /transcode? Depending on the exact technique used, it’ll have a capacity of the total RAM size at the absolute most. Most likely, given the detected capacity of 7.66GB, it is much smaller and doesn’t dynamically change. It has a finite size one way or another and the log line indicates that it had 7.15GB free and the estimate of the size required was 7.65GB. That’s why it didn’t start the transcoder.
agreed, just don’t know why all of a sudden it stopped working on movies, its been fine for 1 year now. This is actually a smaller than normal rip of mine.
