volume.move throws error when using Cloud Tier

[acejam]

Describe the bug
When volumes are stored using Cloud Tier, calling volume.move results in an error. With this configuration, the .dat volume file is stored on S3, but the .vif and .idx files should remain local. volume.move should only attempt to move the .vif and .idx files, but errors when trying to find the .dat file.

> volume.move -source seaweedfs-volume-hdd-3.seaweedfs-volume:8080 -target seaweedfs-volume-hdd-0.seaweedfs-volume:8080 -volumeId 1775

2022/10/07 20:42:35 copying volume 1775 from seaweedfs-volume-hdd-3.seaweedfs-volume:8080 to seaweedfs-volume-hdd-0.seaweedfs-volume:8080
error: copy volume 1775 from seaweedfs-volume-hdd-3.seaweedfs-volume:8080 to seaweedfs-volume-hdd-0.seaweedfs-volume:8080: rpc error: code = Unknown desc = failed to copy /data/seaweedfs/volume2/cache_1775.dat file: receiving /data/seaweedfs/volume2/cache_1775.dat: rpc error: code = Unknown desc = open /data/seaweedfs/volume1/cache_1775.dat: no such file or directory

System Setup
SeaweedFS 3.28 on Kubernetes
version 30GB 3.28 901e815 linux amd64

Expected behavior
Calling volume.move results in moving .idx and .vif files only for Cloud Tier volumes.