Although I utilize Tdarr for transcoding H.264 videos to H.265 videos, I do use it in a somewhat off-label manner. Rather than Tdarr watching my main videos folder, I move new H.264 movies from a share on a pool drive to a different share on the same drive that Tdarr watches. This drive originally utilized the XFS file system. This arrangement worked just fine under this scenario and Tdarr’s folder watch picked up newly copied files and placed them into the transcoding queue. In preparation for use of this drive for additional functions, I converted this pool device to ZFS. Now, when I move H.264 videos to the Tdarr watched folder, the folder watch function does not place anything into the transcoding queue. If I initiate a Scan of the Tdarr watch folder/library, the newly copied video is detected, added to the transcoding queue, and transcoding proceeds without issue. My question is, is this simply a result of the natural behavior/function of the ZFS file system and how files are copied and/or moved on a drive, or is there something else amiss here? Due to my low usage of Tdarr, this current behavior is not really a problem as it is only just a few extra mouse clicks. But, I’m interested as to the cause to satisfy my my own personal curiousness.
Additional information…. I am on the most current versions of Unraid and Tdarr both. Also, I am new to the ZFS file system and its more detailed behavior/function.