mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
[10.11-RC4] Migration "XYZ_MoveTrickplayFiles" - "No space left on device" #7227
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#7227
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ireun on GitHub (Aug 7, 2025).
Description of the bug
I've tried to update form 10.10 to 10.11-RC4.
Under 10.10 i've set path for Metadata and Transcoding to (mounted external storage)
/JellyfinData/Metadataand/JellyfinData/Transcodingrespectively.The 10.11 migration checks if there is enough space:
But my Metadata directory is larger then 2GB:
9e88121647/Jellyfin.Server.Implementations/StorageHelpers/StorageHelper.cs (L26)that is checked above, and it is larger then free space for/var/lib/jellyfin/data. So the check was successful but the migration was doomed to fail.Reproduction steps
What is the current bug behavior?
Failed migration
What is the expected correct behavior?
Successful migration
Idea 1: Check against the Metadata folder size, and not hard-coded 2GB
Idea 2: Migrate to the path that was set in settings, if it was changed, and not to
/var/lib/jellyfin/dataJellyfin Server version
Unstable
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.11-RC4
Environment
Jellyfin logs
@Shadowghost commented on GitHub (Aug 7, 2025):
This migration extracts the Trickplay files from the metadata directory into its own directory (like attachments, etc.). Since we're moving files this shouldn't be an issue as long as you don't use different mounts for all the subdirectories.
I guess you're doing exactly that by modifying the main metadata path.
@ireun commented on GitHub (Aug 7, 2025):
Well my understanding is that it was extracting files from
/JellyfinData/(which is externally mounted) into/var/lib/jellyfin/data/(which is on the device).The device is actually an LXC container, limited to 8 GB of storage (since everything heavy is saved externally). So before the migration the files on-the-device weight 3.17 GB files with 4.82 GB of free space.
I intentionally left the .db files and others on-the-device so they would be backed up by Proxmox. This keeps the backups light, by including only critical files. Everything stored externally can be re-created in case of any failure.
@Fenrirthviti commented on GitHub (Aug 18, 2025):
Just wanted to add that I updated my Docker image from :latest
to :10.11.0-rc5 and ran in to a similar issue here. I have not explicitly changed any subdirectories, my Docker compose only has:
I'm getting similar errors here in the log file. First time booting after the image update, I received an error page with the full log, but subsequent restarts refuse to even try and just bootloops indefinitely with the following critical error:
@ireun commented on GitHub (Aug 18, 2025):
I've decided to just expand my LXC volume by 8GB. About 6GB were moved from my external storage, migration was successful. Though I really think this check should be improved, as it may break some jellyfin deployments.
@jellyfin-bot commented on GitHub (Dec 21, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@Fenrirthviti commented on GitHub (Dec 21, 2025):
Confirming at least in my case, I was able to update to 10.11.5 and no longer have these errors, all migrations completed, and nothing is complaining about disk space any longer. All good for me!