adamfl

Was this ever resolved? If I move my data between disks manually, my hard links are fine because I am not intentionally splitting out the subfolders. rsync -aHAXvP --info=progress2 /mnt/disk7/ /mnt/disk3 However, trying something similar in Unbalanced splits all of the top level share folders into separate transfers, thus breaking hard links that all existing with disk7, for example, but are in separate subfolders (tv vs downloads). I'd like to opt out of the -R command and run these transfers at the /diskX folder level instead of one level down. Is that possible? Thank you.

Apropos of nothing (as far as I know), my Parity 2 disk had a big red X and was disabled a day or two ago. I ran the short, and the long SMART tests and both completed without error, so as far as I know the disk is okay? How can I reenable the disk? Attaching diagnostics. Not sure how to attach the SMART log. Thanks. Edit: Found this - https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself Working through that now. rick-diagnostics-20240328-2043.zip

Just wanted to surface this up as I also prefer it to fdupes. Any chance we could get it added?

Hello, I raised a question about the survivability of NFS exported exclusive shares upon reboot here - https://forums.unraid.net/topic/158140-exclusive-mode-deactivating-on-reboot-wnfs-sharing/ NFSv3 appears to work just fine for exporting exclusive shares after the array has been started up. I was wondering why this is not officially supported or if it could be made to be supported at array start? Is there a known issue with this? The moderators in my prior thread recommended I tag @limetech Thank you.

I'll reach out in the NFS subforum. Thanks!

This logically makes sense. I'm not sure I understand *why* this is a limitation, then? There is no problem exporting a symlinked location via NFS?

I am able to successfully export an exclusive share over NFS (v3 only) when sharing is not enabled upon array start, and then I subsequently enable NFS sharing on that share. It works fine. My fstab record on my client specifies NFS v4.2, but it then keeps trying lower versions until it successfully mounts with NFS v3. The issue is that shares do not retain that exclusive status if I do not remove sharing prior to restarting the array, which is annoying, but not insurmountable. @itimpi This appears to be the conditions required for the share to be mounted as such, but the NFS exported portion doesn't seem to matter post array start.

For that share specifically. It was globally left on and has been on for other array based shares throughout, so only share specific settings were changed.

Is it expected behavior that a share which is wholly on a pool in exclusive mode, and has NFS sharing turned on after a reboot, would then lose exclusive mode after a subsequent reboot when NFS sharing is left enabled? I was rebooting to enable exclusive mode on a share which recently had all of its data moved off the array to a pool and two other shares which were previously exclusive are now exclusive=no. They had NFS sharing on during the reboot but no data on the array. If this is expected behavior, I can work around it by disabling NFS on every exclusive share for every array reboot, but if it is not expected, I'm wondering if this can be fixed in the future? Thank you.

Not sure why, but after a second reboot while NFS is off and everywhere on the array was empty, it turned on this time! Thanks.

@JorgeB Rebooting did not resolve this. I verified there is still only content for the share showing on the one pool and in `/mnt/user` but no `/mnt/diskx` locations. Should I post diags? I imagine they would be the same as yesterday?

I didn't, I'm in the middle of my initial parity calculation still. I can do that possibly in 24 hours.

Attached, thanks.rick-diagnostics-20240313-0958.zip

I removed the options and set it to public, reenabled the share export, then disabled it again - unfortunately it's still not showing as exclusive.

Hello all, One share (opt) won't move to exclusive mode. I have a number of exclusive shares working so I don't believe this is a configuration issue. This share I previously had on the array only. I wanted to move it to be exclusive, so I: Switched primary storage to one of my SSD pools Set secondary storage to the array Set mover to move from array to the pool Disabled NFS export on the share Verified there is no content from this share `opt` on any other location by doing a `ls /mnt/*/opt` The results are as such, but exclusive mode isn't flipping to yes. Are there any other ways to trigger it? Thank you. rick-diagnostics-20240313-0922.zip