move: create_parent: error: No space left on device

[harrison.guo]

Timed move failed to move the cache to the array. After the move was executed, the cache disk space was still not released. Check the log and report an error, as shown in Figure 1. However, each hard disk has sufficient space. The minimum available space of the shared folder is set to 0kb, so there is no problem of insufficient space.
Strangely, I use SSH to move the cache disk files to the array hard disk through the command.

The problem still exists after restart

Also attach the diagnostic log

tower-diagnostics-20211117-2212.zip

[Squid]

Because of the naming of the shares I can't open some of the config files for the shares, but you'll want to verify that the cache floor setting is correct for them (it's in KB, not bytes)

 

[harrison.guo]

3 hours ago, Squid said:

Because of the naming of the shares I can't open some of the config files for the shares, but you'll want to verify that the cache floor setting is correct for them (it's in KB, not bytes)

 

thanks，The new diagnosis result has turned off the anonymous option

tower-diagnostics-20211120-0443.zip

[ChatNoir]

@harrison.guo, I did not check all shares, but I see shareInclude="disk2" on some shares.

Witch mean that the files will only go to disk2.

On your picture I only see 1 data drive.

 

Try to remove that from all shares and try mover again.

[harrison.guo]

1 hour ago, ChatNoir said:

@harrison.guo，我没有检查所有共享，但我在某些共享上看到了 shareInclude="disk2"。

女巫的意思是文件只会转到disk2。

在您的图片上，我只看到 1 个数据驱动器。

 

尝试从所有共享中删除它，然后再次尝试移动。

Thank you for reminding me. When sending a new report, I reset the available space of two shared folders to 0KB for saving, and then executed move, and found that they were successfully moved to the array. Your answer also verified that this was the problem. It may be that two disks were used before, and these configurations did not change automatically when the hard disks were removed. I hope this problem can be improved in the future. Thank you!