[Solved] Mover Error: no space left on device

[Daveja-Vu]

I'm a long time Unraid user (forgive the new account) and I've recently run into an issue with 6.12.4 that I've not seen before where I can't get Mover to push things to the array for a specific User Share.  The share in question has 6 disks associated with it, two of which have more than 1TB free. 

 

The share settings are:

Minimum Free Space: 50GB

Allocation Method: High Water

Split Level: Automatically split any directory as required

Mover action: Cache -> Array

 

Originally I had a low Min Free Space (1GB), so I raised it to 50GB, moved some files temporarily off the array, and started filling it back up.  The last three disks in the Included Disks filled up to ~50GB free and then Mover started throwing errors like:

 

Oct 29 15:08:07 Tower move: move_object: /mnt/cache/Videos/TV - US and Canada/Show)/Season 9/Show - s09e04.mkv No space left on device

...and

Oct 29 15:08:07 Tower move: create_parent: /mnt/cache/4kmovies/Movie (2019) error: No space left on device

 

I'm at a bit of a loss because I would think the first two Included Disks that have plenty of space left would be used now that the others have hit the Minimum Free Space, but apparently not.

 

Open to any suggestions - I may be misunderstanding a setting here. Thanks!

Edited October 30, 2023 by Daveja-Vu
Marked as solved

[itimpi]

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

[Daveja-Vu]

Diagnostics attached, performed immediately after reboot and 'Move' button clicked with logging enabled.  Thanks for any advice.

 

Edited October 30, 2023 by Daveja-Vu

[JorgeB]

You are running into a bug when using included disks, it doesn't write to all included disks, bug will be fixed for next release, for now you can remove all included disks or use excluded disk instead.

[Daveja-Vu]

Just changed the two shares to use excluded disks instead of included as suggested, and things are working as expected now.  Thanks for the workaround, JorgeB!