starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #11464] Add Env Var to disable WAL journaling #12902

New Issue
Closed
opened 2026-02-07 07:03:47 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 07:03:47 +03:00
Owner
Copy Link

Original Pull Request: https://github.com/jellyfin/jellyfin/pull/11464

State: closed
Merged: No

Changes

SQLite WAL journaling is not compatible with all filesystems/VFS extensions, causing the database being locked up in certain conditions.

It's worth noting that database lockup is just one potential issue that can arise from compatibility issues with certain filesystems. In some cases, the use of WAL can even lead to the database being saved in a non-consistent state, resulting in database corruption.

Add an env var to let the user to choose the Journal mode for better compatibility.

For example, when the default WAL is causing problems:

export JELLYFIN_SQLITE__JOURNALMODE=TRUNCATE

Issues

**Original Pull Request:** https://github.com/jellyfin/jellyfin/pull/11464 **State:** closed **Merged:** No --- <!-- Ensure your title is short, descriptive, and in the imperative mood (Fix X, Change Y, instead of Fixed X, Changed Y). For a good inspiration of what to write in commit messages and PRs please review https://chris.beams.io/posts/git-commit/ and our documentation. --> **Changes** <!-- Describe your changes here in 1-5 sentences. --> SQLite WAL journaling is not compatible with all filesystems/VFS extensions, causing the database being locked up in certain conditions. It's worth noting that database lockup is just one potential issue that can arise from compatibility issues with certain filesystems. In some cases, the use of WAL can even lead to the database being saved in a non-consistent state, resulting in database corruption. Add an env var to let the user to choose the Journal mode for better compatibility. For example, when the default WAL is causing problems: ``` export JELLYFIN_SQLITE__JOURNALMODE=TRUNCATE ``` **Issues** <!-- Tag any issues that this PR solves here. ex. Fixes # -->
OVERLORD added the pull-request label 2026-02-07 07:03:47 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
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
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#12902
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?