"Found # remote files that are not recorded in local storage, please run repair" using NAS as destination

[crypdick]

Thanks Ken. I agree, it’s bizarre that it worked for so long and then suddenly started prompting me that remote files were missing and to repair. Perhaps Duplicati has a task that runs seldomly that doesn’t handle this edge case? It seems clear at least that the “repair” functionality doesn’t handle this edge case.

My last successful backup was Friday of last week and I just noticed today that my daily backups had been failing.

I can understand not wanting to make a breaking change for current users. I think a minimally invasive change would be a warning message or “are you sure?” dialog if someone tries to use a leading slash.

[kenkendk]

@crypdick

it’s bizarre that it worked for so long and then suddenly started prompting me that remote files were missing and to repair. Perhaps Duplicati has a task that runs seldomly that doesn’t handle this edge case? It seems clear at least that the “repair” functionality doesn’t handle this edge case.

My last successful backup was Friday of last week and I just noticed today that my daily backups had been failing.

There has been no Duplicati updates in that timespan.
Perhaps @wasabi-jim knows if there are changes to Wasabi in that period?

@crypdick

I can understand not wanting to make a breaking change for current users. I think a minimally invasive change would be a warning message or “are you sure?” dialog if someone tries to use a leading slash.

Yes, that could be a good soft-guard.

[ts678]

I’m not sure what the industry standard (if there is one) for object storage is for odd pseudo-folder cases that can’t happen in a normal filesystem. Basically, you can but slashes anywhere, but what do they do?

Wasabi “The requested folder does not exist” #4696 wants bucket root. Should Path be a forward slash?

Backup files missing on Wasabi (cited earlier) found that tools such as Cyberduck got confused by slash.

Keys with double slashes are invisible #6757 (Cyberduck) rejected supporting those, citing S3 examples.

No files with the backup prefix duplicati, but found the following backup prefixes: uplicati #4711 (on Storj) used a leading forward slash, and that confused things.

The same questions could potentially arise for any object storage pseudo folders, not just S3 compatible.

When planning solutions, maintaining ability to reach whatever wound up as the key was mentioned, but there’s also a command line to worry about, where anything can be typed, and user interaction is limited.

I’d also point out that double slash means different things. If in a URI, I’d guess one gets stripped off, so from a key point of view it’s a singled leading slash. On the other hand, you can double slash in the path, but that’s a more obvious thing to not do. Whether or not GUI Path needs leading slash is not very clear.

Generally I advise no extra leading or trailing slashes. I think that’s the maybe-unstated GUI Path intent.

[wasabi-jim]

hi @kenkendk @crypdick - there haven’t been any recent changes @ Wasabi that would have caused this sort or thing but if you have specific questions, please drop a note to support at wasabi.com and we can look into any account speciifc concerns - thx!

[kenkendk]

@crypdick

t’s bizarre that it worked for so long and then suddenly started prompting me that remote files were missing and to repair. Perhaps Duplicati has a task that runs seldomly that doesn’t handle this edge case?

Since Wasabi was not updated, my best guess is that you have hit the unwanted downgrade bug. This happens occasionally when “something” touches the files in the update folder, and Duplicati considers the update invalid. You can check the version reported by Duplicati and see if it still reports the version you expected.