Yes. I forgot that. In fact I didn't know that was necessary.
I managed to put the old system up again. The installed s3ql version is
2.12.
In order to check if the fs mounts and since I had changed the oauth2
token, I had to update the old auth file:
Old:
[gs]
storage-url: gs://ideiao-bkp
backend-login: oauth2
backend-password: 1/Lely6ZhHlSUna_BWBCXEJremOJz0tXfjsnSb7gMrygo
fs-passphrase: ***********
New:
[gs]
storage-url: gs://ideiao-bkp
backend-login: oauth2
backend-password:
1/mo6BOlKCGIJhkIJCg3ZGjlLE6XyxesggPybESUTDuPtIgOrJDtdun6zK6XiATCKT
fs-passphrase: ***********
*The size of the token is completely different... Is this normal?*
In the old system, when mounting with the new authfile, I get:
mount.s3ql --authfile /root/scripts/.s3ql_authinfo2 --cachedir /root/.s3ql/
gs://ideiao-bkp /media/1/
Using 10 upload threads.
Autodetected 4034 file descriptors available for cache entries
Requesting new access token
Using cached metadata.
Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/local/bin/mount.s3ql", line 9, in <module>
load_entry_point('s3ql==2.12', 'console_scripts', 'mount.s3ql')()
File
"/usr/local/lib/python3.4/site-packages/s3ql-2.12-py3.4-linux-x86_64.egg/s3ql/mount.py",
line 130, in main
(param, db) = get_metadata(backend, cachepath)
File
"/usr/local/lib/python3.4/site-packages/s3ql-2.12-py3.4-linux-x86_64.egg/s3ql/mount.py",
line 391, in get_metadata
db = Connection(cachepath + '.db')
File
"/usr/local/lib/python3.4/site-packages/s3ql-2.12-py3.4-linux-x86_64.egg/s3ql/database.py",
line 71, in __init__
cur.execute(s)
File "src/cursor.c", line 990, in APSWCursor_execute.sqlite3_prepare
File "src/statementcache.c", line 386, in sqlite3_prepare
apsw.CorruptError: CorruptError: database disk image is malformed
and verifying gives this:
s3ql_verify --debug --authfile /root/scripts/.s3ql_authinfo2 gs://ideiao-bkp
2016-01-04 00:06:53.978 10013 MainThread
s3ql.backends.common.get_ssl_context: Reading default CA certificates.
2016-01-04 00:06:53.986 10013 MainThread
s3ql.backends.gs._get_access_token: Requesting new access token
2016-01-04 00:06:59.197 10013 MainThread s3ql.backends.s3c._do_request:
preparing GET /s3ql_passphrase?None, qs=None
2016-01-04 00:06:59.197 10013 MainThread s3ql.backends.s3c._send_request:
_send_request(): GET /s3ql_passphrase
2016-01-04 00:07:04.647 10013 MainThread s3ql.backends.s3c._do_request:
preparing GET /s3ql_passphrase?None, qs=None
2016-01-04 00:07:04.648 10013 MainThread s3ql.backends.s3c._send_request:
_send_request(): GET /s3ql_passphrase
2016-01-04 00:07:10.261 10013 MainThread
s3ql.backends.common.get_ssl_context: Reading default CA certificates.
2016-01-04 00:07:10.268 10013 MainThread s3ql.backends.s3c.list:
list(s3ql_seq_no_, ): start
2016-01-04 00:07:10.268 10013 MainThread s3ql.backends.s3c.list:
list(s3ql_seq_no_): requesting with marker=
2016-01-04 00:07:10.268 10013 MainThread s3ql.backends.s3c._do_request:
preparing GET /?None, qs={'marker': '', 'prefix': 's3ql_seq_no_',
'max-keys': 1000}
2016-01-04 00:07:10.268 10013 MainThread s3ql.backends.s3c._send_request:
_send_request(): GET /?marker=&prefix=s3ql_seq_no_&max-keys=1000
2016-01-04 00:07:15.820 10013 MainThread s3ql.backends.s3c.lookup:
lookup(s3ql_seq_no_100)
2016-01-04 00:07:15.820 10013 MainThread s3ql.backends.s3c._do_request:
preparing HEAD /s3ql_seq_no_100?None, qs=None
2016-01-04 00:07:15.820 10013 MainThread s3ql.backends.s3c._send_request:
_send_request(): HEAD /s3ql_seq_no_100
2016-01-04 00:07:16.230 10013 MainThread s3ql.backends.s3c.lookup:
lookup(s3ql_seq_no_100)
2016-01-04 00:07:16.230 10013 MainThread s3ql.backends.s3c._do_request:
preparing HEAD /s3ql_seq_no_100?None, qs=None
2016-01-04 00:07:16.230 10013 MainThread s3ql.backends.s3c._send_request:
_send_request(): HEAD /s3ql_seq_no_100
2016-01-04 00:07:16.604 10013 MainThread s3ql.backends.s3c.lookup:
lookup(s3ql_seq_no_101)
2016-01-04 00:07:16.605 10013 MainThread s3ql.backends.s3c._do_request:
preparing HEAD /s3ql_seq_no_101?None, qs=None
2016-01-04 00:07:16.605 10013 MainThread s3ql.backends.s3c._send_request:
_send_request(): HEAD /s3ql_seq_no_101
2016-01-04 00:07:17.077 10013 MainThread s3ql.mount.get_metadata: Using
cached metadata.
2016-01-04 00:07:17.078 10013 MainThread root.excepthook: Uncaught
top-level exception:
Traceback (most recent call last):
File "/usr/local/bin/s3ql_verify", line 9, in <module>
load_entry_point('s3ql==2.12', 'console_scripts', 's3ql_verify')()
File
"/usr/local/lib/python3.4/site-packages/s3ql-2.12-py3.4-linux-x86_64.egg/s3ql/verify.py",
line 103, in main
(param, db) = get_metadata(backend, cachepath)
File
"/usr/local/lib/python3.4/site-packages/s3ql-2.12-py3.4-linux-x86_64.egg/s3ql/mount.py",
line 391, in get_metadata
db = Connection(cachepath + '.db')
File
"/usr/local/lib/python3.4/site-packages/s3ql-2.12-py3.4-linux-x86_64.egg/s3ql/database.py",
line 71, in __init__
cur.execute(s)
File "src/cursor.c", line 990, in APSWCursor_execute.sqlite3_prepare
File "src/statementcache.c", line 386, in sqlite3_prepare
apsw.CorruptError: CorruptError: database disk image is malformed
What can I do?
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.
