# Instant DB corruption

**URL:** <https://forums.plex.tv/t/instant-db-corruption/938271>\
**Category:** Metadata & Adding Files\
**Tags:** server-linux\
**Created:** [April 24, 2026, 12:11am UTC](https://forums.plex.tv/t/instant-db-corruption/938271 "2026-04-24T00:11:07Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![pshanew](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/pshanew/32/160555_2.png) [@pshanew](https://forums.plex.tv/u/pshanew)\
**Post date:** [May 2, 2026, 9:58am UTC](https://forums.plex.tv/t/instant-db-corruption/938271/7 "2026-05-02T09:58:20Z")

</div>

Indeed, it always appears to be corrupted after a scan. I think it’s because of how PMS rebuilds the indexes (or doesn’t) itself after scans. [It seems to do it _lazily_, not in realtime.](https://forums.plex.tv/t/dbrepair-development/822684/935) It’s unfortunate as it leads to these kinds of misunderstandings.

The net result is that the full-text search functionality may not have the most up-to-date information. But the database is not corrupted in any way even if reported as such (for the FTS tables).

---

_[View the full topic](https://forums.plex.tv/t/instant-db-corruption/938271)._