I suspect this is because you copied the objects into a new bucket, but
did not include the associated metadata.
Which tool did you use to do the copy, and how did you call it?
I used the AWS command line tools:
aws s3 sync s3://src-bucket s3://dest-bucket
It did fail part way through the transfer, so I restarted it with the same
command.
When you use the S3 Management Console
(https://console.aws.amazon.com/s3/home) to look at the "s3ql_metadata"
object in the original bucket and the copy, does it have the same
metadata?
While the s3ql_metadata file is there, in the new bucket it is missing all
of the keys except the Content-Type. Not sure whether this means the fsck
without cached data trashed it, or if amazon's sync was trashing the
transfered data because I used it incorrectly or it is broken somehow.
Shannon C. Dealy | DeaTech Research Inc.
de...@deatech.com | - Custom Software Development -
USA Phone: +1 800-467-5820 | - Natural Building Instruction -
numbers : +1 541-929-4089 | www.deatech.com
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
