version 7.1.2

Without having 'overwrite existing files' selected, it seems that unraid still is overwriting existing files when using the web UI's move functionality.

I don't know if this is a bug or intended behavior, but it has caused me to accidentally overwrite thousands of files that had the same name instead of either aborting the operation, pausing to inform/confirm, or renaming the files.

Steps to recreate:
inside of a directory, create a test file: 'a.txt' with content Hello World
copy the file to another directory
in the original directory change the content of the file, without changing anything else Hello World 1
using the unraid web UI select the move option, ensure overwrite existing files is un-selected.
see that a.txt has been overwritten with the new content.

While I will obviously stop using the unraid UI for any and all file transfer operations moving forward, I am wondering what process Unraid uses under the hood to do these moves and if the files are lost or not.

Edited June 4, 20251 yr by adrianedelen

I am going to guess that the GUI move on the webui just uses mv but doesn't specify something like -n for no clobber. If that is the the case i would consider it a bug, since the web GUI afaik can only be (and is intended to be) accesses by the root user, there can be some unexpected scenarios that happen.

Edited June 5, 20251 yr by adrianedelen
typo

54 minutes ago, adrianedelen said:

just uses mv

Pretty sure it uses rsync, but I cannot reproduce, copying from one disk to another, please give the exact steps you are using.

On 6/5/2025 at 10:07 AM, JorgeB said:

Pretty sure it uses rsync, but I cannot reproduce, copying from one disk to another, please give the exact steps you are using.

I am not copying from one disk to another explicitly. I am using the webUI move tool to move files and directories between shares and directories within shares.

here are the steps to reproduce in details:
1. create a new share with two directories src and dest.

2. In srccreate a text file hello_world.txt with the content new_content

3. In dest create a text file hello_world.txt with content old_content

4. using the file move tool, ensuring overwrite existing files is disabled/unselected move src/hello_world.txt to dest

Expected behavior:
the software will abort, throw an error, pause, alert the user, or otherwise intercept the transfer, due to the mismatch in content.

Actual behavior:
the content in dest/hello_world.txt is overwritten old_content -> new_content

Here is a link to a video showing the behavior, the quality ended up being quite low, Im unsure why that is, but it shows the overwriting in action.
demo

I'm afraid that I still cannot reproduce:

Before copying:

Copy using

After copying:

If I select the overwrite existing files option:

2 hours ago, JorgeB said:

I'm afraid that I still cannot reproduce:

@adrianedelen did say that he was using the 'move' option and not the 'copy'.

I've been able to reproduce it with the move operation between 2 shares on the same drive, destination is exclusive source is not, did not further test whether that matters.

Edited June 9, 20251 yr by Kilrah

46 minutes ago, Frank1940 said:

did say that he was using the 'move' option and not the 'copy'.

Ahh, missed that part.

OK, with move I can reproduce, I was always trying with copy before, thanks for the report, I'll report it to LT.

Thanks everyone for looking into this.

This should be fixed in 7.1.4, please retest.