CodeMonkeyX

I just wanted to say that this update did break NFS for my situation. I went back after a few days and read the change log to try and figure out if something changed that broke it and saw this: I only use NFS to store jobs archived on a old production printer (Xerox Docutech 6135 from the 90's), and unRAID worked great until that update. Thankfully the setting "Tunable (support hard links)." fixed the problem for me. I just wanted to say please don't ever remove that option! I know people who want it are an edge case, but it really would ruin my year if I had to try and implement and maintain a vm or docker or something just to run a NFS server for those old machine.

I was trying to do this recently and think I may have found a different way that is a little more foolproof. I wanted to move my appdata share from "disk1" to the "cache." What I did was this: 1. Shutdown the Plex Docker. 2. Change the "appdata" user share cache setting from "no" to "Prefer." (From help docs for Prefer: When the mover is invoked, files and subdirectories are transferred off the array and onto Cache disk/pool.) 3. Run the Mover. 4. Change the "appdata" user share cache setting from "Prefer" to "Only." That seemed to do what was explained here, and avoided using the command line.