aawsome

@Cookie04DE Thanks for opening this issue! I have a question: How should rustic check if the repository is writable? The point is, currently writing fails after rustic tries to write...

> If compatible with current constraints, I would suggest to make rustic open the necessary files in write mode at the very start of the backup produce without writing anything...

@simonsan See my first answer. I would strongly vote against such a "throw-away" or garbage file. However we could add an an optional feature to mimic restic's locking (create a...

@Cookie04DE Thanks for your results. So, yes, you have many new or changed files which explains why pretty much data is written. And I guess you have quite a large...

@intgr IMO it is not about whether it is possible to do the one or other check, I think we simply should not do such checks in rusitc, see my...

I'm closing this issues as we will not add direct support to rustic and a workaround is possible using a `run-before` hook.

To tackle the problem I'd like to summarize the technical details and also start a discussion about possible solutions. ## Cause of high memory usage - Basically the main problem...

Actually rustic should write the config file into the cold storage location as `DEEP_ARCHIVE`, if it is specified like that. While rustic will not access any file/object in the cold...

Actually another test to rule out any permission stuff would be to run the same config without using `default_storage_class` and see if the error still exists...

Thanks for opening this issue @kkettinger This is actually how opendal is working, see https://opendal.apache.org/docs/rust/opendal/services/struct.S3.html. We can't fix this in rustic. If you want to have it fixed, can you...