disk space usage for transcoding-temp

[CChris 59]

Hi,
I've setup my new emby server within a virtual container in Proxmox.

 

Suddenly, emby stopped the playback.
I've tried to change the user, since my user (login via ldap) does not have administrative permissions - but, I was not able to login with the local admin user.
I just got the error, that the server could not reached.

 

After having a look into the system monitor for this container, I noticed, that the root drive, where debian and emby is installed showed over 90% disk usage.
I thought, 8 GB should be enought, but I changed the setting to 12 GB.

After rebooting the container, I could continue with the movie - until it stopped again.

 

The same issues like before, I could not change the user.
Again, the root disk with now 12 GB of space was nearly full 95% usage - and, after rebooting the machine, the emby software could not start.

 

I run the command du -a /var | sort -n -r | head -n 5 to get a list of the folders with the biggest size on the disk.
The output showed /var/lib/emby/transcoding-temp/ as the biggest folder - and, after deleting all files from transcoding-temp, the disk usage is now only 12%

 

I could start the emyb server again and everything is working fine, but it seems, that emby does not clean up the transcoding-temp folder until the system is out of resources.
 

Is this an expected behave?
Or should I install a cron, which deletes all the files from time to time?

Or what is the recommended disc size for such an installation?

 

Thanks and with best regards,
Christoph

[Sammy 790]

Are you throttling the transcode?

 

Sent from my SM-G960U1 using Tapatalk

[Luke 42078]

The next release will do a better job of cleaning them up, but generally speaking, the transcoding temp folder needs to be at least as large as whatever media you're playing.

 

Future releases can reduce this requirement, albeit with more transcoding - meaning if you seek back and forth it may have to re-transcode due to the previous output being deleted to preserve disk space.

[Sammy 790]

The next release will do a better job of cleaning them up, but generally speaking, the transcoding temp folder needs to be at least as large as whatever media you're playing.

 

Future releases can reduce this requirement, albeit with more transcoding - meaning if you seek back and forth it may have to re-transcode due to the previous output being deleted to preserve disk space.

 

Is this adjustable? I transcode to a dedicated 128GB SSD when transcoding is needed and would rather have fast seek times.

[CChris 59]

Ok, thanks for the information.
I will change the settings for the emby container and provide more space for it.