On Apr 20 2015, Rich B <[email protected]> wrote:
> Hello,
> I've been using Google Storage for my backend for a while now and decided
> to experiment with their new "near line" storage.
> I tried using gsutil to copy the contents of my s3ql bucket to a new
> nearline bucket. I updated my authinfo2 file, but the moved filesystem
> won't fsck:
>
> $ fsck.s3ql gs://my-new-bucket/mys3qlfs
> MD5 mismatch in metadata for s3ql_passphrase
> MD5 mismatch in metadata for s3ql_passphrase
> MD5 mismatch in metadata for s3ql_passphrase
> Encountered BadDigestError exception (BadDigest: Meta MD5 for
> s3ql_passphrase does not match), retrying call to Backend.open_read for the
> 3-th time...
> MD5 mismatch in metadata for s3ql_passphrase
> Encountered BadDigestError exception (BadDigest: Meta MD5 for
> s3ql_passphrase does not match), retrying call to Backend.open_read for the
> 4-th time...
>
> Did something get copied wrong, or is this expected result? Is there
> another supported way to do this that doesn't require a download and
> reupload cycle?
Most likely gsutil did not copy the metadata. Does it work if you use
contrib/clone_fs.py? (Try it with a small test file system first).
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.
