Jeff Bogatay <[email protected]> writes:
>> If you are comfortable doing that, could you check if you get the
>> same error if you run fsck.s3ql with --backend-options no-ssl?
>
> no-ssl worked. The fsck completed and I was able to mount it. Is this
> a quirk of AmazonS3 or something? The regular mounted operations work
> fine.
Not really, it works fine for many people. If you have time to debug
this further, could you maybe try to get a traffic dump with Wireshark
when the error occurs?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
