I can see the issue again. I enabled --rc on the machines so i can refresh the vfs cache but it does not care about it. It seems that there is another cache wich is not refreshed. I remove also the track-renames stuff and it still comes up again.
What I am doing:
ls /"new_path"/file.txt #this works
cat /"new_path"/file.txt
Input/output error
rclone log says:
vfs cache: failed to download: vfs reader: failed to write to cache file: failed to open for download: -> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, github.com/Azure/azure-storage-blob-go@v0.10.0/azblob/zc_storage_error.go:42
===== RESPONSE ERROR (ServiceCode=BlobNotFound) =====
Description=The specified blob does not exist.
RequestId:20067330-a01e-0070-5e82-ee2a00000000
Time:2021-01-19T16:43:49.4167029Z, Details:
Code: BlobNotFound
GET https://"old_path"
Authorization: REDACTED
User-Agent: [rclone/v1.53.2]
X-Ms-Client-Request-Id: [e06e3116-fa47-4af5-75bc-ae11c4cdcdd7]
X-Ms-Date: [Tue, 19 Jan 2021 16:43:49 GMT]
X-Ms-Range: [bytes=0-650196]
X-Ms-Version: [2019-02-02]
RESPONSE Status: 404 The specified blob does not exist.
Content-Length: [215]
Content-Type: [application/xml]
Date: [Tue, 19 Jan 2021 16:43:48 GMT]
Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0]
X-Ms-Client-Request-Id: [e06e3116-fa47-4af5-75bc-ae11c4cdcdd7]
X-Ms-Error-Code: [BlobNotFound]
X-Ms-Request-Id: [20067330-a01e-0070-5e82-ee2a00000000]
X-Ms-Version: [2019-02-02]
rclone rc vfs/refresh dir="old_path"
"file does not exist"
rclone rc vfs/refresh dir="new_path"
"file does not exist"
rclone rc vfs/forget dir="old_path"
"forgotten": "old_path"
rclone rc vfs/forget dir="new_path"
"forgotten": "new_path"
But still when I want to access the file in the new path it says input/putput error. The directory structure is properly. It is in the new path, but when I want to access a file in the directory it tries to connect to the old location.
Do i miss something in my flags regarding a parallel caching mechanism?
Thanks