May 07 15:57:58 MOVED_FROM => /mnt/disk5/data/t----s/r----s/B----OG/s-----31.bin.partial
May 07 15:57:58 MOVED_TO => /mnt/disk5/data/t----s/r----s/B----OG/s-----31.bin
May 07 15:57:58 ATTRIB => /mnt/disk5/data/t----s/r----s/B----OG/s-----31.bin
May 07 15:57:58 OPEN => /mnt/disk5/data/t----s/r----s/B----OG/s-----31.bin
May 07 15:57:58 DELETE => /mnt/disk5/data/t----s/r----s/B----OG/s-----31.bin

 

 

Mover seems to be moving the data from disk5 to disk5 and then deleting it when running:

mover start -e disk5 |& logger &

 

 

Am I using it incorrectly?

plexraid-diagnostics-20250508-0000.zip

Edited May 8, 20251 yr by MowMdown

I just added two drives to my array with the intent to move the data off two other drives and then remove the initial two for repurposing. After reading the release notes, the mover utility still takes your config settings into effect. Making me wonder if you have most-free set for your share(s). Perhaps your disk 5 has the most free space and your share settings are set to most-free. I could potentially see this as an issue to where it would move it off disk 5 and onto disk 5, then delete the file. If this is the case, almost seems like the mover utility need to exclude the source disk you are moving off of.

 

I was thinking about playing it safe and excluding my two disks I'm pulling out from the shares before running it. But now I'm scared to lose anything.

Share setting for data is set to high water, however disk5 did have the most free space.

 

i just wouldn’t think this would try to move existing data to the same disk.

 

I even excluded disk5 from all shares and re-ran it to see if that would work, same result.

10 hours ago, MowMdown said:

Am I using it incorrectly?

Do you have the mover tuning plugin installed? If yes, uninstall it first.

3 hours ago, JorgeB said:

Do you have the mover tuning plugin installed? If yes, uninstall it first.

 

Nope, do not have mover tuning plugin installed.

Please post the diagnostics.

As you may have noticed, we just fixed my xfs disk mounting issue in that other thread, those are the only diagnostics I currently have as I gave up with the mover to empty disk after I confirmed it deleted data from disk5 without  moving it to the other disks. All in all Ilist about 40GB, not a major loss and I was able to recover it.

Here is the scenario in which it occurred. Disks 1-4 were approximately 50%, 50%, 70% and 50% full respectively. Disk 5 was 17% full. I wanted to use mover to empty disk5 so I could convert it to parity2. All shares are set to highwater, all disks were included, nothing excluded. Mostly unraid default settings.

I ran mover on disk5 to empty it, and at first I found it odd that only disk5 was being both written to and read from. I stopped mover and thought it had deleted some data. Parent folders did appear on other disks just nothing inside them.

 

I decided to exclude disk5 from all shares and re-ran mover again, this time one of my shares respected this and the data successfully moved to disk1. my "data" share however did not. It resumed what it did previously, writing data to itself (disk5) and then removing the completed file as if it thought it moved it to another disk. Which you can see at the top of the post logs from File Activity plugin.

 

Mover did log a bunch of successful moves of said deleted data. I however am not willing to re-create the scenario on my array again.

 

 

Edited May 8, 20251 yr by MowMdown

I don't see the mover tuning plugin installed, but those log messages are not stock mover messages, suggesting to me that something is interfering with it, normal mover logging looks like this:

 

May  8 15:36:49 Test5 root: mover: started
May  8 15:36:50 Test5 root: move: /mnt/disk1/data/A Success
May  8 15:36:50 Test5 root: move: /mnt/disk1/data/B Success
May  8 15:36:50 Test5 root: move: /mnt/disk1/data/C Success
May  8 15:36:50 Test5 root: move: /mnt/disk1/data/D Success
May  8 15:36:50 Test5 root: move: /mnt/disk1/data/E Success
May  8 15:36:50 Test5 root: mover: finished

 

Those messages are from the file activity plugin, not from mover or syslog.

 

Mover was in fact operating as I was seeing "move success" messages throughout the operation.

 

For example:

 

mover: /mnt/disk5/data/t----s/r----s/B----OG/s-----31.bin sucesss

 

I believe mover was moving the file from disk5 to disk5 due to it having the most free space and a "s-----31.bin.partial" file occupied the same location by evidence of the file activity log (highwater allocation selecting disk5 as the available disk to use)

 

IMO to fix this, mover needs to have a check that it does not move the files to the same disk they currently occupy. If Im running "mover start -e disk5 |& logger &" then mover needs to exclude disk5 from it's operation.

Edited May 8, 20251 yr by MowMdown

Here is the relevant syslog, I found a backup copy. Everything listed as "successful" was deleted except for the appdata backup files, for whatever reason those moved properly after I made a share change to "split any directory as required" from "manual"

 

Data share split level is "top 3" and I didn't change that.

 

I stopped mover, excluded disk5 from all shares, I noticed parent folders started showing up on disk1 but the files themselves did not move to disk1.

syslog.txt

 

Edited May 8, 20251 yr by MowMdown

Thanks for the details, I'll see if I can reproduce.

I think I can reproduce, it's related to the split-level, anything below it is correctly moved, anything above disappears, I've reported the issue to LT.

Not that it matters since you have keyed in on the issue. I am in the process of moving disk 2 so I can remove it. I excluded it from all my shares beforehand. I just checked my split is set as what I believe is default. "Automatically split any directory as required". Mover has been running for several hours and everything is looking good.

32 minutes ago, UncleStu said:

Not that it matters since you have keyed in on the issue. I am in the process of moving disk 2 so I can remove it. I excluded it from all my shares beforehand. I just checked my split is set as what I believe is default. "Automatically split any directory as required". Mover has been running for several hours and everything is looking good.

 

That's good, the only share I had set to automatic worked, the others didn't.

8 hours ago, UncleStu said:

"Automatically split any directory as required". Mover has been running for several hours and everything is looking good.

Should be, the problem appears to only affect if there's a split level set, and any data above that split level

6 hours ago, JorgeB said:

Should be, the problem appears to only affect if there's a split level set, and any data above that split level

Can you post your example of what you mean by "above" because my situation was appeared to be levels 4 and 5 were the issue but levels 1-2-3 seemed to work fine when split was set to level 3 (in my mind i'd consider levels 4 and 5 are "below" or deeper than level 3)

 

I just want to get a better idea of what you found the issue to be on your end.

Edited May 9, 20251 yr by MowMdown

20 minutes ago, MowMdown said:

in my mind i'd consider levels 4 and 5 are "below" or deeper than level 3

Yep, that's what I meant, deeper levels than the split level set (if not set to auto) are the ones that show the issue.

I know this issue was Patched but does anyone know what versions of unraid were effected by this bug?
Reason I am asking is because I am on version 7.0.1 and Thought I was save and used the Mover to empty a drive and I'm very sure it deleted a whole hardrive worth of data. Luckily it was just TV shows.

Edited May 13, 20251 yr by Bfox135

6 hours ago, Bfox135 said:

what versions of unraid were effected by this bug?

It's mentioned in the release notes: 7.1.0 and 7.1.1, 7.0.1 is not affected.

 

 

 

 

18 hours ago, JorgeB said:

It's mentioned in the release notes: 7.1.0 and 7.1.1, 7.0.1 is not affected.

 

 

 

 

well it very much is cause I ran the mover on 7.0.1 and now I have about 4tb of shows missing from the drive it was moving the shows too....
every episode expect for the one's it moved.

5 hours ago, Bfox135 said:

well it very much is cause I ran the mover on 7.0.1 and now I have about 4tb of shows missing from the drive it was moving the shows too....

It's certainly not the same bug, since it's very easy to reproduce, and it only starts with 7.1.0-beta.2 and newer, but there could be another one, though I would find it strange no one else running into it, but it may be a very corner case, if you can post array and share config you were using I can try to reproduce.