Mover does not use "reconstructive write" anymore

[desertfox_0815]

Hello @ all 

my mover wont use reconstructive write anymore. disk settings are correct and not changed.

Running unraid 6.12.13

do you have any idea what i need to do to get it back working again?

mover was running very fast with approx. 220mb/s lately until now...

already rebootet and switched disk settings to "auto" and back to "reconstructive write" - did not help

diag is attached.

 

thanks alot for your help

tower-diagnostics-20240919-1153.zip

Edited September 19, 2024 by desertfox_0815
attached unraid version

[desertfox_0815]

screenshot of mover running

 

 

disc settings

 

[desertfox_0815]

same mover job and suddenly it uses full speed

will monitor it if it switched back to "auto"

 

[JorgeB]

First screenshot show writes to multiples disks, turbo write is temporarily disabled when that happens, when it starts witting to a singe disk it should enable again.

[desertfox_0815]

Just now, JorgeB said:

First screenshot show writes to multiples disks, turbo write is temporarily disabled when that happens, when it starts witting to a singe disk it should enable again.

 

no second write was happening during mover running at the time of the screenshot.

[JorgeB]

It shows writes to disks 1 and 3 at the same time, turbo write will be disabled.

[desertfox_0815]

yeah but only mover was running and copying large files.

 

[JorgeB]

It doesn't matter what is doing the writes, with writes to more than one disk 

16 minutes ago, JorgeB said:

turbo write will be disabled.

 

[desertfox_0815]

ok i will analyze the prozesses on os level if a second mover was running due to some strange happenings.

thanks alot

[JonathanM]

2 hours ago, desertfox_0815 said:

ok i will analyze the prozesses on os level if a second mover was running due to some strange happenings.

thanks alot

Mover isn't the only thing that will write to drives, if an existing file is overwritten, the writes will happen on the disk where the file exists.

[desertfox_0815]

14 hours ago, JonathanM said:

Mover isn't the only thing that will write to drives, if an existing file is overwritten, the writes will happen on the disk where the file exists.

i know. im a longtime user and it-senior-admin so the way unraid works is not new to me.

and this is the reason why this behavior caught my attention.

 

no other write was happening during this mover run. i was consolodating files from one share to another share reading from array and writing to the new shares cache pool.

after this process i was running mover to move the files to array.

 

i will have a look at every single mover process in the near future.