Vacuum: invalid cross-device link

[KevinBLT]

Describe the bug
I thought it was a clever idea to have the index files on another hard drive than the data.
But that lead to errors while committing vacuum. The files are now shown with 0 bytes.

Can I somehow "restore" them or are they completely gone??

System Setup
Two mounted devices:
/meta is an NVME and /data is a "normal" SSD.

Command:

weed server -dataCenter=app1 -ip=app1 -master.dir=/meta -master.peers=app1:9333,app2:9333,app3:9333 -dir=/data -volume.dir.idx=/meta -volume.index=leveldbLarge -volume.max=0 -rack=1 -filer.encryptVolumeData -volume.fileSizeLimitMB=4096 -master.volumeSizeLimitMB=1024 -filer.defaultReplicaPlacement=100 -filer.saveToFilerLimit=4096 -filer

Version: 3.52

Expected behavior
I could live with a warning/error or something but SeaweedFS should try to handle that without losing data at least.

Screenshots

topology_vacuum.go:138 Error when committing vacuum 3 on app1:8080: rpc error: code = Unknown desc = rename /meta/3.ldb: rename /data/3.cpldb /meta/3.ldb: invalid cross-device link
volume_grpc_vacuum.go:87 failed commit volume 3: rename /meta/3.ldb: rename /data/3.cpldb /meta/3.ldb: invalid cross-device link