I've started noticing this new error in my backup logs since upgrading to s3cmd version 2.0.0 when using sync mode. The backup appears to still complete succcesfully with no other errors.