Emby Server service keep writing to disk

[emme1967e 0]

Hi,

I was analyzing my disk writes using block_dump and discovered that Emby-Server is continuously writing to the disk even when ther is absolutely no activity from the users.

 

Here is a partial syslog:

Nov 19 19:44:12 openmediavault kernel: [787238.454127] EmbyServer(4684): dirtied inode 2100132 (server-63646646400.txt) on sda1
Nov 19 19:44:12 openmediavault kernel: [787238.454149] EmbyServer(4684): dirtied inode 2100132 (server-63646646400.txt) on sda1
Nov 19 19:44:12 openmediavault kernel: [787238.454151] EmbyServer(4684): dirtied inode 2100132 (server-63646646400.txt) on sda1
Nov 19 19:44:12 openmediavault kernel: [787238.454189] EmbyServer(4684): WRITE block 7570592 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.454806] jbd2/sda1-8(208): WRITE block 109333232 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.454822] jbd2/sda1-8(208): WRITE block 109333240 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.454924] jbd2/sda1-8(208): WRITE block 109333248 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.460172] EmbyServer(4684): WRITE block 7570592 on sda1 (16 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.460639] jbd2/sda1-8(208): WRITE block 109333256 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.460667] jbd2/sda1-8(208): WRITE block 109333264 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.460683] jbd2/sda1-8(208): WRITE block 109333272 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.460695] jbd2/sda1-8(208): WRITE block 109333280 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.460707] jbd2/sda1-8(208): WRITE block 109333288 on sda1 (8 sectors)
Nov 19 19:44:12 openmediavault kernel: [787238.461118] jbd2/sda1-8(208): WRITE block 109333296 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.522161] EmbyServer(4684): WRITE block 7570600 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.523176] jbd2/sda1-8(208): WRITE block 109333304 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.523211] jbd2/sda1-8(208): WRITE block 109333312 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.523442] jbd2/sda1-8(208): WRITE block 109333320 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.534468] EmbyServer(4684): WRITE block 7570600 on sda1 (16 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.535287] jbd2/sda1-8(208): WRITE block 109333328 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.535319] jbd2/sda1-8(208): WRITE block 109333336 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.535341] jbd2/sda1-8(208): WRITE block 109333344 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.535353] jbd2/sda1-8(208): WRITE block 109333352 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.535365] jbd2/sda1-8(208): WRITE block 109333360 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.535595] jbd2/sda1-8(208): WRITE block 109333368 on sda1 (8 sectors)
Nov 19 19:44:15 openmediavault kernel: [787241.555853] EmbyServer(4684): WRITE block 7570608 on sda1 (8 sectors)

As soon as I stopped the service, all the writes to the disk stopped.

 

Any reason the Emby Server keeps writing to the disk?

 

[Luke 37184]

Hi there, please attach the emby server log. you can learn how to do that here:

 

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks.

[emme1967e 0]

Hi there, please attach the emby server log. you can learn how to do that here:

 

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks.

 

Here it is

 

thanks

server-63646646400.zip

[Luke 37184]

Is this from the same time period as the system log you captured?
 

If so, unfortunately i can't see anything obvious here. can you try to find what files updated? maybe it was just the server log file?

[emme1967e 0]

Hi,

yes same period.

The log file closed when I stopped the service.

Something abnormal should be there as the log file is 26MB in just 20 hours...

And it contains a lot of errors...

 

It definitely could be that it was the server log file. But how can I stop it from writing to the disk? Can I change it's location to /tmp that is in tempfs location?

[Luke 37184]

The location is not configurable. you could try turning off dlna features in the emby server dashboard.

[mastrmind11 717]

yes, turn off dlna.  that shit blows up like crazy.