Disk Utilization High

[Spyderturbo007 19]

@PaulE123 You’re not the only one having this issue. I’ve narrowed it down to Emby as well and I can almost reproduce it. It’s always related to me trying to move through a video too quickly.  It’s weird because I’m not even transcoding, just direct play. 

I’ve been in the server when it says it’s at 99% and when I open the container size it’s normal. 
 

unRAID showed me that my docker RAM usage was at 99% when it was happening. Another thing I’ve noticed is that it seems to correspond to Emby showing that it’s streaming a movie but it isn’t.  I stop playing the movie on the shield, but but Emby says it’s still streaming. 
 

I’m on my phone so I can only upload a few screenshots which probably aren’t helpful. I can post more detailed information when I’m at a workstation.  

Edited November 26, 2022 by Spyderturbo007

[Luke 42085]

Hi @Spyderturbo007 

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[Spyderturbo007 19]

Hi @Luke 

Here is what I did to get the log file.

1. Stopped and started the Emby docker container

2. Rebooted the Shield

3. Rotated the log file

4. Began playback of a movie named Black Friday.  Stats for nerds showed Direct Play.

5. Used the skip forward button a bunch of times after the movie started playing.  This causes the video to freeze for ~2 minutes while the CPU utilization goes through the roof (all attributed to Emby) and the docker image generates the error below.

6. When the movie started playing again it showed that it was transcoding for some reason.

7. I then exited the movie.  Within a minute or two I received the message "Docker utilization returned to normal" message from my server.

 

Event: Docker critical image disk utilization

Subject: Alert [TOWER] - Docker image disk utilization of 99%

Description: Docker utilization of image file /mnt/cache/system/docker/docker.img

Importance: alert

embyserver.txt

[Happy2Play 9783]

If am interpreting this correctly your docker.img needs increased as transcoding temp fills the img size, until then transcode-temp folder is cleaned up.

But yes something crashes direct play.

TranscodeReasons=DirectPlayError,DirectPlayError

 

[Luke 42085]

@Spyderturbo007 has this answered your question? It looks like you are transcoding after all and perhaps you don't have enough space for it?

[PaulE123 20]

On 12/4/2022 at 1:53 AM, Luke said:

@Spyderturbo007 has this answered your question? It looks like you are transcoding after all and perhaps you don't have enough space for it?

Luke, in my case, the docker file is 30GB in size. Not sure if @Spyderturbo007changed his default size or not, but if not, that's still a 20GB img file....i don't understand how a movie file can fill it up, transcoded or not. Increasing the size of the file just seems like putting a plaster over an open wound

Edited December 5, 2022 by PaulE123

[Luke 42085]

17 minutes ago, PaulE123 said:

Luke, in my case, the docker file is 30GB in size. Not sure if @Spyderturbo007changed his default size or not, but if not, that's still a 20GB img file....i don't understand how a movie file can fill it up, transcoded or not. Increasing the size of the file just seems like putting a plaster over an open wound

When transcoding you may need to allocate space that is at least the size of the original video.

[PaulE123 20]

18 hours ago, Luke said:

When transcoding you may need to allocate space that is at least the size of the original video.

Indeed, and the only movie sizes I have that size are 4k variants which are in a separate libraries, and unshared to wan users. So the only times this has happened to me have been when wan users are accessing media which is nowhere near the 30GB docker.img size. 

Edited December 6, 2022 by PaulE123