# Transcode runner appears to have died (automatic conversion) **URL:** \ **Category:** Plex Media Server\ **Tags:** server-unraid, android-mobile-legacy\ **Created:** [March 12, 2025, 12:32pm UTC](https://forums.plex.tv/t/transcode-runner-appears-to-have-died-automatic-conversion/908680 "2025-03-12T12:32:06Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\ **Post date:** [April 13, 2025, 10:59pm UTC](https://forums.plex.tv/t/transcode-runner-appears-to-have-died-automatic-conversion/908680/12 "2025-04-13T22:59:22Z")
@kerbys This is a local host issue. When using docker, we can’t see what’s happening with the host filesystem. The best I can give you are the Linux Tips. (for fs.inotify.max\_user\_watches) > [@Linux Tips](https://forums.plex.tv/t/linux-tips/276247/9): > > Increase the number of directories Linux can monitor (inotify) for PMS The default size of the Linux inotify table is 8192 directories (\*1). When PMS is configured to update automatically when media is added, with properly organized media, especially music, this table rapidly fills and exceeds the default allocation requiring you to increase it. The solution to this is straight forward. Increasing the table size is easy. The first step is to determine how many directories to alloca… I will share that my experience with BTRFS has not been favorable. I’ve watched many Synology users lose their entire storage volume (media and PMS) due to BTRFS. IMHO, it has not proven itself to be stable My personal choice is the one proven by enterprise servers – xfs. It’s more robust and a heck of a lot faster. It also scales VERY well. FWIW: 12x 12TB HDDs, RAID 6, xfs format, pulls 2.0-2.1 GB/sec --- _[View the full topic](https://forums.plex.tv/t/transcode-runner-appears-to-have-died-automatic-conversion/908680)._