[HUGE PROBLEM] Add Media Library TRIGGERS "Scanning all Library" #4213

Closed
opened 2026-02-07 00:34:53 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @vegedb on GitHub (Sep 20, 2022).

Adding any library will trigger a FULL SYSTEM SCAN.

This shouldn't be the case as the other libraries are TOTALLY UNRELATED when adding a new library. And a prevention that will cause a total system wipe.

Example of a problem,

  1. Current Library has Movies/TV shows already PERFECTLY scraped.
  2. Scheduled Library Scan is turned OFF.
  3. One day you decide to add a "Home Movies" Library.
  4. You unplug the drive momentarily or accidentally that has your Movies/TV shows and plug in your "Home Movies" drive.
  5. You add library as per normal
    image
  6. You wait for the "Scan" to finish
  7. After some time, you find that all your databases are WIPED and require another scan.

So please, could you disable this scanning feature whenever a NEW library is added.

Originally created by @vegedb on GitHub (Sep 20, 2022). Adding any library will trigger a **FULL SYSTEM SCAN.** This shouldn't be the case as the other libraries are TOTALLY UNRELATED when adding a new library. And a prevention that will cause a total system wipe. Example of a problem, 1) Current Library has Movies/TV shows already PERFECTLY scraped. 2) Scheduled Library Scan is turned **OFF**. 3) One day you decide to add a "Home Movies" Library. 4) You unplug the drive **momentarily or accidentally** that has your Movies/TV shows and plug in your "Home Movies" drive. 5) You add library as per normal ![image](https://user-images.githubusercontent.com/72070424/191224301-1be20ae3-0fcf-43f5-8b00-4828d423d2cc.png) 6) You wait for the "Scan" to finish 7) After some time, you find that all your databases are WIPED and require another scan. So please, could you disable this scanning feature whenever a NEW library is added.
OVERLORD added the stale label 2026-02-07 00:34:53 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (Jan 19, 2023):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot commented on GitHub (Jan 19, 2023): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#4213