Sorry about the post etiquette (or lack of it).
Guess what? Problem solved. I was not aware that I was using the default
location of the cachedir. Weather I defined the parameter or not, the
corrupted cache was always been used!
On the old server, I ran fsck, without any errors. Now going to move to the
new system, and do the upgrade.
Many thanks.
domingo, 3 de Janeiro de 2016 às 04:45:57 UTC, Alexandre Gonçalves escreveu:
>
> Hello,
>
> I had a google storage mount running for several months, with any issue.
> (v 2.12).
>
> The computer broke down, and I'm migrating the storage unit to another
> server. When mounting the first time, using the same credentials, I got:
>
> sudo mount.s3ql --authfile /s3ql/auth/s3ql_authinfo2 gs://ideiao-bkp
> /s3ql/gstore/
> Using 8 upload threads.
> Autodetected 4040 file descriptors available for cache entries
> Requesting new access token
> Uncaught top-level exception:
> Traceback (most recent call last):
> File "/usr/local/bin/mount.s3ql", line 9, in <module>
> load_entry_point('s3ql==2.15', 'console_scripts', 'mount.s3ql')()
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/mount.py",
>
> line 120, in main
> options.authfile, options.compress)
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/common.py",
>
> line 340, in get_backend_factory
> backend.fetch('s3ql_passphrase')
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/backends/common.py",
>
> line 351, in fetch
> return self.perform_read(do_read, key)
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/backends/common.py",
>
> line 107, in wrapped
> return method(*a, **kw)
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/backends/common.py",
>
> line 314, in perform_read
> fh = self.open_read(key)
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/backends/common.py",
>
> line 107, in wrapped
> return method(*a, **kw)
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/backends/s3c.py",
>
> line 307, in open_read
> meta = self._extractmeta(resp, key)
> File
> "/usr/local/lib/python3.4/dist-packages/s3ql-2.15-py3.4-linux-x86_64.egg/s3ql/backends/s3c.py",
>
> line 715, in _extractmeta
> raise CorruptedObjectError('Invalid metadata format: %s' % format_)
> s3ql.backends.common.CorruptedObjectError: Invalid metadata format: pickle
>
> Thinking that it might be an issue of tokens, I ran s3ql_oauth_client to
> create a new token, but the problem is the same.
>
> The command fsck.s3ql gives similar results.
>
>
> How can solve this? Thanks.
>
>
>
>
>
>
--
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.
