[SQLite DB Corruption testers needed]

I just had my first ever instance of sabnzbd corruption today. My appdata is /mnt/user/appdata/sabnzbd and my data disks are all formatted as xfs. 

2019-07-24 12:20:52,064::ERROR::[database:142] Damaged History database, created empty replacement
2019-07-24 12:22:12,507::ERROR::[database:142] Damaged History database, created empty replacement
2019-07-24 12:23:17,987::ERROR::[database:142] Damaged History database, created empty replacement
2019-07-24 13:00:17,803::ERROR::[database:142] Damaged History database, created empty replacement
2019-07-24 13:00:17,823::ERROR::[database:142] Damaged History database, created empty replacement
2019-07-24 13:00:18,162::ERROR::[database:154] SQL Command Failed, see log

 

[Downgraded back to 6.6.7 due to Sqlite corruption]

I have now had two Plex database corruptions in the last 30min with the second one being somewhat intentional. I am starting with a fairly new Plex appdata directory as my previous database backups became corrupted so I chose to start over fresh. Today I downloaded a new media file and copied it to /mnt/user/movies and shortly thereafter tried to play the new media file and which failed and I found database corruption. So I restored to my most recent backup and tried adding another new media file. This media file was automatically discovered by Plex during the copy process to /mnt/user/movies. No corruption occurred until I refreshed the Plex On Deck page which started to show the new media file and at this point I see corrupt database error messages in the Plex logs.

 

My appdata share only resides on disk2. I do have a cache disk and have confirmed that no appdata directory is present on the cache drive. My Plex docker container is configured to use /mnt/disk2/appdata/plex. My system is still running 6.7.0.

 

Edited to add, all non-cache disks are formatted XFS