What is the minimal partitionning system disk for Linux Debian please

[ReididNomis 1]

What is the matter ?

1) - I installed Emby Server on a Debian Light Linux machine (no graphical interface)

2) - I have two disks:

- The first is for the system.

- The second one (2 TB) contains all my media files (images, videos, etc.).

3) - My system partitioning is

EFI partition: 1 GB

/boot partition: 1 GB

Root partition / : 10 GB

Swap partition: 8 GB (equivalent to the size of the RAM)

/home partition: 4 GB

4) What am I observing?

I don't know how to explain it, but the file system / sometimes/often becomes full (100% occupied).

I think the /var/lib/ directory fills up over time.

I just upgraded Emby Server to version 4.9.1.80 ==> OK.

Running the upgraded version quickly saturated the file system /

5) - The question is: What is the optimal partitioning for managing Emby Server on Linux Debian ?

I think the partitioning I chose isn't suitable for my needs.

I've searched the Emby documentation and the forum without finding any answers.

Luke, can you please advise us : What is the optimal system partitioning for managing Emby Server?

Thank you in advance

Reidid Nomis

 

 

 

[tollgate 8]

I'm no expert on partition sizes, but I would say your root partition needs to be at least 50G. 

[Q-Droid 989]

There's no one size fits all answer and too many factors will determine how much space you'll need for Emby. If you want to avoid a system hang due to filling up the root partition my suggestion is to add a 10GB /var partition which is where most of the Emby configuration and runtime data goes as well as that for other applications and services you might be running. Depending on what else you're running this might not be enough.

I have a modest size media library and my emby home (/var/lib/emby) directory is 6.5GB which also contains the cache and metadata files (defaults). 

 

[tedfroop21 86]

Are you backing up your media disk by chance? 

Or moving data to a mounted drive automatically some other way?

It is possible if the drive mount drops the drive that the data would copy to your mnt or media directory and fill your partition.

There is a simple fix. 

1. Run a shell script instead of directly running rsync (or whatever copy you are using)

2. Make the following the start of the script.  Replace /media/Nas3 with your mount file name.

df | grep -q /media/Nas3
if [ $? = 0 ]; then

This makes sure the mount is connected before backing up or moving data.

[TMCsw 247]

Other things to look at (to use less space on the root drive):

1. Transcoding Temporary path (this can take a lot of space when needed, put it on the 2TB drive)
2. In library settings, make sure "Keep a cached copy of images in the server's metadata folder" is off.