vrtmrz
entry not found, maybe deleted (it is normal behavior)
Hi,
I'm seeing a ton of these and I don't know how to correct quickly. Nothing is shown in Corrupted or missing data. How do I address this? Please advise.
Sorry for this, The expression was too much as it came to mind. My laziness.
This means
We keep the deleted document for history and diff, but it could not be extracted without explicit parameters. So it shall be failed to extract to the storage. Then it acts as same as the case that the entry was found and suddenly deleted and had been not found while in the boot sequence. So it is expected and normal behaviour.
However, it had been a so rude message, I fixed this at v0.16.5. (Just retrieving with the parameter and judging correctly) Could you please try this version?
Okay, what should I do when I see the adjusted message? Is this the delete meta flag I need to set?
This message can be ignored. Just history has been detected.
(But I have begun to think this message should be shown as a verbose one...)
History of deleted metadata can be removed by enabling Delete metadata of deleted files (immediately when we deleted the files) or Delete old metadata of deleted files on start-up (after configured days passed).
Yeah, that is a good idea. Will it conflict with choosing a conflict file? I asked a similar question on another item. Sorry for the duplicate.
Delete metadata of deleted files will remove metadata on deletion. But if the conflict occurs again after synchronisation, it will be detected (CouchDB is amazing).
Even if we have dismissed the message at this time, we can open the conflict-resolving dialogue by Pick a file... later.
However, if we left the conflict of deleted files and it has been cleaned up at start-up. it might be completely erased.