For better or worse, these errors don't seem related to the use of S3QL. (S3QL seems more intolerant of them than some other S3-compatible tools, but its behaviour seems quite sensible to me.) I'm seeing them with 's3cmd sync' between two buckets on StorageQloud as well, unfortunately.
I am continuing to pursue the issue with GreenQloud support. It's a shame if S3QL can't be used with them, given that they specifically highlighted it as a use case for StorageQloud. Regards, Adam -- 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.
