Jellyfin Corruption2025-08-04

Yesterday I started streaming from my Jellyfin instance and some time in it completely went away. Turns out the VM disk filled up. After resizing it on the host and guest, the service still failed to start. The error was System.InvalidOperationException: There is an error in XML document (0, 0).. After searching most people say the whole database is corrupt, but in this case it was just the migrations.xml file, which I restored from backup and it started up correctly afterwards. The future Jellyfin 10.11.0 appears to add a check to prevent starting when less than 2GB of disk space is available.

As for why it ran out of disk space, streamed video was being remuxed for compatibility which was taking up disk space and the default option does not immediately remove old parts unless the setting Dashboard > Playback > Transcoding > Delete segments is enabled. Additionally it writes to the actual disk by default instead of /tmp since most systems likely lack enough space there.

Back to blog index