Temporary errors on Wasabi S3 cause filesystem to unmount

unread,

Dec 18, 2021, 4:48:31 AM12/18/21

to s3ql

Good day,

I am using Wasabi as backend and every now and then there is a seemingly "temporary" backend error, which causes the filesystem to be unmounted.

Is this expected behaviour or should s3ql simply wait until the backend becomes available again?

I have seen two distinct errors so far:

TemporarilyUnavailable: Resources for this operation are temporarily unavailable. Please try again later.

TemporarilyUnavailable: Storage service is temporarily not available. Please try again later (name: UnexpectedError | detail: ConnWaitError)

Logs attached for context.

Best,

Bas

wasabi-mount.log

unread,

Dec 18, 2021, 7:47:32 PM12/18/21

to s3ql

Hello Bas,

I am using Wasabi as backend and every now and then there is a seemingly "temporary" backend error, which causes the filesystem to be unmounted.

[...]
Logs attached for context.

This is fixed by https://github.com/s3ql/s3ql/pull/258
This change did not make it into a release yet. Either wait for a new release or change the two lines of https://github.com/s3ql/s3ql/pull/258/files in your local S3QL sources.

unread,

Dec 19, 2021, 4:31:54 AM12/19/21

to s3ql

Oh excellent, thank you. I missed that one.

Reply all

Reply to author

Forward