On Mar 11 2021, "Brian C. Hill" <[email protected]> wrote:
> On 3/11/21 5:37 PM, Brian C. Hill wrote:
>> Hello,
>>
>> All of the list discussions on cloning that I found deal with cloning
>> between local and
>> remote locations.
>>
>> I want to clone my s3ql fs from one AWS S3 bucket to another AWS S3 bucket.
>>
>> I used the awcli sync command, but mount.s3ql thinks new fs bucket is
>> corrupted, and
>> fsck.s3ql won't fix it.
>>
>> The s3qlcp command will only work within the same filesystem.
>>
>> Mounting both filesystems and using cp or rsync will take days to copy.
>>
>> I am running clone_fs.py now to the bucket that I already formatted the dest
>> fs on,
>> which I don't think will work, and it looks like it will take 9 hours to
>> complete.
>>
>> What is the fastest way to do this?
>>
>> Brian
>>
>
> The clone_fs.py step took 4 hours and seemed to succeed (a s3cmd du showed
> that all of the
> objects had been copied), but no files appear when the filesystem is mounted,
> probably
> because the local metadata doesn't account for them). An fsck.s3ql scans
> through the
> correct the number of objects but decides that none of them should be there
> and starts
> deleting them.
>
> Is there must be some small adjustment to make mount.s3ql properly recognized
> the cloned
> copy?
Try to just delete the local metadata in ~/.s3ql.
Best,
-Nikolaus
--
GPG 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/87tupg5p29.fsf%40vostro.rath.org.
