vtmikel

The UI gives me an error but does in fact save with the trailing "/". This was needed for me to get SSO to work with Authentik.

My understanding is that hardlink preservation is working correctly under 7.1.4 as long as the hard-link is in the same user share. per this: https://forums.unraid.net/bug-reports/stable-releases/unraid-714-mover-not-working-since-upgrade-r3991/#findComment-35025 Is there reason to believe, outside of this, that hardlink preservation via the mover with mover tuning, are broken? This would be a big problem for me.

Prior to 7, I was able to mount a NFS export for a pool via /mnt/<pool>/<share>. The share does not have a secondary storage, but it's not marked exclusive, I think due to the note in the 6.12 release notes: If a share is NFS-exported it cannot be exclusive, i.e., the syslink is not created. This is because symlinks are resolved in the NFS client, not the server. We hope to lift this restriction in a future update. After upgrade I am only able to mount /mnt/user/<share> Am I correct that /mnt/user will have a lower performance due to FUSE? Is it intentional to not allow export of /mnt/<pool>/<share>?

Does the LXC have NFS enabled in Options -> Features?

Reading up on this plugin for the first time. Is the Sanoid plugin not safe or recommended for Unraid 7? I'm interested in implementing policy based snapshots, is there an alternative?

RC8 seems to have relocated the move binary to /usr/local/bin from /usr/local/sbin

Hi- Did a reinstall, same result. Dashboard is inaccessible, same with the plugin config. I have to uninstall the plugin to be able to return to the dashboard. Any debug I can provide?

Hello- I’ve seen references to the 6.12 RC’s in this thread, is the plugin intended to work with 6.12? Upon installing the Unraid dashboard does not load for me (completely blank), and I am unable to get to the plugin configuration either.

I have performed a run of the mover using the fixed age_mover. Hard linked files were maintained.

I can confirm that my hardlinks were lost for many (potentially all? Though to tell) files moved since the update. I used jdupes to identify the duplicate files that were once hard links (took 24 hours due to the size of the share). Good news is, jdupes is reporting exact copies, so no corruption. I'm happy to provide my logs if it helps. Question / Request: with the new architecture, is it possible for the mover to only move files, based on criteria in the tuning plugin, up til the threshold being met, and then stop? Or, does it already work like this?

Did something change with respect to how hard links are handled? After the upgrade to the plugin, mover ran for a very long time and my hard links seems to have been unlinked and the content is duplicated.