I have a problem that I have been trying to solve, described here :

Someone on Reddit replied saying they did not know the answer but had asked ChatGPT!

I went to the chat and after a few back and forths, ChatGPT said:

The core rule you accidentally violated (everyone does once)

Never move, rename, or delete parent directories inside /mnt/user when the directory is split across disks.

Unraid cannot safely do what you asked it to do.

essentially, you can't do that! That is, you can move a directory around inside a share if the share contains more than one disk.

I have never heard that and, in fact, I'm pretty sure I have done just that. Or maybe I was just lucky and when I did move directories,

I just happened to never move one that was split across disks?

Can someone point me to the Unraid documentation where this very common action is no allowed?

No this doesn't make any sense.

User shares are created from the top level folders on array and pools each time the array starts.

BS AI hallucination.

But your paths are wrong, so it's hard to know what you actually did that could have caused issues.

What you must not do is copy/move between /mnt/user (shares) and /mnt/diskX or vice versa.

Edited January 12Jan 12 by Kilrah

I have been running unRaid since 2008. I know not to copy from share to disk or vice versa.

As to what I did wrong, I still have no idea. Chatgpt said you can't do this:

mv /mnt/user/Backup1/backups/Tower/Home\ Video/dashcam /mnt/user/Backup1/backups/Tower/dashcam

this should move the dashcam directory up one level in the share and also in the disks that are included in the share right?

I would expect it to keep the files on the disk they are already on and just "repath".

Along with so-called "user share copy bug", that was another of those "surprising" things with user shares. If you try to move to another user share, it would just "repath" the file on the same disk, possibly violating settings for the target user share such as excluded disks. Maybe that is what AI is "thinking of".

I know you are moving to the same user share, but I think the "repath" should still apply.

Just now, trurl said:

If you try to move to another user share, it would just "repath" the file on the same disk, possibly violating settings for the target user share such as excluded disks.

The workaround for that case was to copy from source to destination, so the write obeys the rules for the destination, then delete the source.