I'm not sure how I've screwed this up, but I've been experimenting with integrating rclone into IDrive e2 and hit a snag.
I set up a mount and have been playing with moving a few files back and forth, figuring out how to automate the mount, that sort of thing. Now when I mount the drive with this command
rclone mount e2:backup1/ ~/mnt/ --vfs-cache-mode writes -vv
I get a whole string of errors about the cache. I'm not sure how I deleted things from the cache, because I don't know where the cache is. What I have done is deleted things directly in the IDrive E2 web interface.
This set of four lines is repeated for hundreds of files. I trimmed them to keep the size of the pastebin down. I think it's all the files I deleted.
2022/08/18 17:49:13 DEBUG : media/MP3/Wood Brothers/Ways Not To Lose/10 Angel Band.mp3: vfs cache: truncate to size=7739272
2022/08/18 17:49:13 DEBUG : media/MP3/Wood Brothers/Ways Not To Lose/10 Angel Band.mp3: vfs cache: setting modification time to 2013-03-04 16:12:25 +0000 UTC
2022/08/18 17:49:13 INFO : media/MP3/Wood Brothers/Ways Not To Lose/10 Angel Band.mp3: vfs cache: queuing for upload in 5s
2022/08/18 17:49:13 ERROR : media/MP3/Wood Brothers/Ways Not To Lose/10 Angel Band.mp3: vfs cache: failed to reload item: reload: failed to add virtual dir entry: file does not exist
UPDATE:
Today, when I tested the command, it didn't generate all those errors. I've done nothing to fix it.
Can anybody share any light on why this happens. I've seen one other post about this same error that didn't seem to get resolved. Is it the case that this will happen in certain situations, particularly if you're testing workflows like I was? Something like if the drive isn't mounted for long enough, the cache can't sort itself out so just needs time?