BUG: Debian install doesn't check for insufficient partition space

[markshu 7]

The Debian version of emby server uses /var for most of its data store. If Debian was installed on a single partition (default) this causes no issues as /var is just a subdirectory in the system partition. However, more experienced Linux admins will install Debian with separate root, /usr, /var, and /home partitions, and the /var partitions are usually limited in space.  One of the 'standard' Debian install options creates a root partition of 10GB that includes both /usr and /var, with the remaining disk space partitioned for /home.

 

With a separate /var partition, the default emby server settings will quickly exhaust the available partition space storing metadata, images, and creating temp files for transcoding.  Once /var is exhausted, none of the Debian desktop GUIs will launch and emby cannot transcode to clients.  Having to reinstall Debian to cerate a single system partition is not a reasonable solution.

 

The Linux emby server installs should never assume that /var space is unlimited, and must check for sufficient free partition space before allowing the install to complete.  Any minimum partition space requirements should be stated up front in either the Wiki or during installation.

Edited August 30, 2015 by markshu

[fc7 123]

Sorry but I don't agree this is a bug. Emby package never assumes unlimited space on any partition.

If there is no space left in /var (or in any other path that Emby package requires to put the files in) then the package manager should and will abort installation.

 

If you have enough space for installation but not to hold your library files, etc. then you can always move Emby directory in /var/lib to any other place in your system with enough free space and use the configuration file emby-server.conf in /etc to point Emby server to the new data path.

 

Then it's up to the system administrator to monitor partitions free space and administer the system accordingly.

[Luke 37053]

Plus the installation is tiny, space doesn't start accumulating until run-time and space consumed depends highly on usage patterns and what your various settings are. And every path that does accumulate a decent amount is available to be changed within the web interface.