I know this is a bad idea but has anyone else copied new video files to their Emby media server while it was in use? Seems to work fine with a SSD or if all drives you use are SSDs!

[ng4ever 40]

Does not work well with a normal 5400 rpm or 7200 rpm hard drive obviously.

 

 

[Happy2Play 9785]

Depending on setting ie Realtime Monitor, this could cause issues as the server could be trying to import media that is not full available so you end up with bad information and have to  manually Refresh the item at a later time.

If you don't use RTM then as long as you are not moving media at/during scan time you should be fine.

But setup and server usage are other factors.

[Guest]

There would also be bottlenecks in transferring the data, from your motherboard and hard drives... over a network - possibly even worse. old slower drives trying to read and write data at the same time used to cause basic playback issues.. coupled with the old motherboards.. you could get stuttering.. just like trying to rip a CD, and listen to music off the drive your writing to at the same time..

I seem to get along fine on Windows 10.. and my NAS doing both.. If I remember I know I can copy movies and write through the same RJ45 to another drive at the same time without a glitch.

Keep an eye on CPU Resources as well.. might show the culprit.

Edited March 31, 2021 by Guest

[Sammy 790]

I've never even considered this question. All my drives are 5400RPM drives in a 54Tb pool and there aren't any issues.

Edited March 31, 2021 by Sammy

[PenkethBoy 2068]

have never seen this issue at all - and i have copied thousands of files to my server while it was active and with rtm ON

if you server has issues with this - its not emby

[ng4ever 40]

Ok just to make sure everyone understands me whore is emby installed ?

 

I am talking about when emby is installed on the same drive as the media files.

[rbjtech 5285]

It depends - if you are trying to stream multiple high bitrate 4K files or transcoding for example while copying 100's of GB's worth of data to a single drive - then yes, it is going to struggle - but this is a bottleneck of your I/O system - it has nothing to do with Emby.

In this scenerio, you need to split the I/O across multiple drives so they have the ability to work in parallel, rather than having to wait for the drive to finish it's I/O operation - ie sequential.