S3Drive - Backblaze - Issues with Trash, Versioning & Sync

Hello, I have an issue with recovering files from Trash. Doing it via the Restore option in file's menu doesn't work. It can be only done via a workaround, which is opening the version list of the file in Trash and delete all of its latest zero-byte versions. After this the file is recovered. The same applies for Delete forever, when Versioning is turned off. This happens only with Backblaze S3 backend (e.g. Wasabi works without issues). I have tried every possible bucket setting, but without luck. I am using S3Drive for Android. Thanks in advance for your support.

Hi @FunnyMarty, Thanks for your feedback. We haven't forgot about that one, but we didn't have chance to look at it. We certainly aim to reproduce and fix it one way or another. When you say:

The same applies for Delete forever, when Versioning is turned off.

I assume that your bucket is versioned, it's just you refer to Versioning setting on the S3Drive side?

Tom

Hi @FunnyMarty, Thanks for your feedback. We haven't forgot about that one, but we didn't have chance to look at it. We certainly aim to reproduce and fix it one way or another. When you say:

The same applies for Delete forever, when Versioning is turned off.

I assume that your bucket is versioned, it's just you refer to Versioning setting on the S3Drive side?

Hi @Tom, Yes, I do. It doesn't matter whether Versioning is enabled in the S3Drive app or not. If a file ends up in Trash, the issue occurs. Regarding the Backblaze side, I've tried setting bucket's File Lifecycle to Keep all versions and to Keep only the last version, but with no change for both settings. If I have correct info, you can't entirely disable versioning on a bucket from Backblaze. Have you managed to reproduce this issue?

Hi @FunnyMarty, we've reproduced this problem and implemented a fix which will be released in next version. The issue was that Backblaze handles encoding/decoding differently than other providers, however technically we were wrong with the S3 specification, it's just other providers were more forgiving. Thank you for reporting this bug!

Tom

Hi @FunnyMarty, we've reproduced this problem and implemented a fix which will be released in next version. The issue was that Backblaze handles encoding/decoding differently than other providers, however technically we were wrong with the S3 specification, it's just other providers were more forgiving. Thank you for reporting this bug!

Hi @Tom, That is great news!

I hope this fix will also solve following issues with versioning I ran into. When I use tasks in Sync tab to sync files, it often happens that the same version of a file is uploaded multiple times. The file then ends up with several versions, one after another, containing identical content. This happens on Android. I haven’t seen the same behavior on Windows yet. Yesterday, I noticed that one of my tasks correctly deleted hundreds of files, but when I tried to permanently delete them from the Trash, I got an error. As a result, the files got stuck in the bucket. When this happens, the files have to be deleted manually (unless a bucket lifecycle policy is set up), because they are no longer shown in Trash in S3Drive. Unfortunately, the logs don’t say much, as I didn’t have debug logging enabled.

#2857 Failed: Error: Deleting 470 out of 1750 object versions has failed. Check logs for more details.
#2858 Error prompt: Failed: Error: Deleting 470 out of 1750 object versions has failed. Check logs for more details.
#2859 DeleteObjects with Errors: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DeleteResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <Error>
        <Code>InternalError</Code>
        <Key>REDACTED</Key>
        <Message>We encountered an internal error. Please try again.</Message>
        <VersionId>REDACTED</VersionId>
    </Error>
...

Thanks again for looking into this.

FunnyMarty

Hi @Tom, That is great news!

I hope this fix will also solve following issues with versioning I ran into. When I use tasks in Sync tab to sync files, it often happens that the same version of a file is uploaded multiple times. The file then ends up with several versions, one after another, containing identical content. This happens on Android. I haven’t seen the same behavior on Windows yet. Yesterday, I noticed that one of my tasks correctly deleted hundreds of files, but when I tried to permanently delete them from the Trash, I got an error. As a result, the files got stuck in the bucket. When this happens, the files have to be deleted manually (unless a bucket lifecycle policy is set up), because they are no longer shown in Trash in S3Drive. Unfortunately, the logs don’t say much, as I didn’t have debug logging enabled.

#2857 Failed: Error: Deleting 470 out of 1750 object versions has failed. Check logs for more details.
#2858 Error prompt: Failed: Error: Deleting 470 out of 1750 object versions has failed. Check logs for more details.
#2859 DeleteObjects with Errors: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DeleteResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <Error>
        <Code>InternalError</Code>
        <Key>REDACTED</Key>
        <Message>We encountered an internal error. Please try again.</Message>
        <VersionId>REDACTED</VersionId>
    </Error>
...

Thanks again for looking into this.

UPDATE: I emptied the entire Trash, which contained a few files, for the same bucket, and I got a message saying that hundreds of files were deleted. The files that were stuck (not shown in Trash, but existing in the bucket) are gone now. I presume that triggering the emptying of the entire Trash will delete even files that are not shown in it.

FunnyMarty

Hi @Tom, That is great news!

I hope this fix will also solve following issues with versioning I ran into. When I use tasks in Sync tab to sync files, it often happens that the same version of a file is uploaded multiple times. The file then ends up with several versions, one after another, containing identical content. This happens on Android. I haven’t seen the same behavior on Windows yet. Yesterday, I noticed that one of my tasks correctly deleted hundreds of files, but when I tried to permanently delete them from the Trash, I got an error. As a result, the files got stuck in the bucket. When this happens, the files have to be deleted manually (unless a bucket lifecycle policy is set up), because they are no longer shown in Trash in S3Drive. Unfortunately, the logs don’t say much, as I didn’t have debug logging enabled.

#2857 Failed: Error: Deleting 470 out of 1750 object versions has failed. Check logs for more details.
#2858 Error prompt: Failed: Error: Deleting 470 out of 1750 object versions has failed. Check logs for more details.
#2859 DeleteObjects with Errors: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DeleteResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
    <Error>
        <Code>InternalError</Code>
        <Key>REDACTED</Key>
        <Message>We encountered an internal error. Please try again.</Message>
        <VersionId>REDACTED</VersionId>
    </Error>
...

Thanks again for looking into this.

Hi @FunnyMarty, Fix is released on Android.

I hope this fix will also solve following issues with versioning I ran into.

Regarding your other issues we'll need to investigate. Thanks.

1

Tom

Hi @FunnyMarty, Fix is released on Android.

I hope this fix will also solve following issues with versioning I ran into.

Regarding your other issues we'll need to investigate. Thanks.

@Tom, Thank you for fixing the file recovery, it works now.

However, similar to what I mentioned above regarding sync, when you restore a file from Trash, its latest non-zero-byte version is duplicated.

FunnyMarty

@Tom, Thank you for fixing the file recovery, it works now.

However, similar to what I mentioned above regarding sync, when you restore a file from Trash, its latest non-zero-byte version is duplicated.

Thanks, we'll look into this, once I know something I will let you know. (edited)

1

FunnyMarty changed the channel name: Backblaze - Issues with Trash, Versioning & Sync 12/24/2025 10:45 PM