Dear Nikolaus,
Thank you for your time. I've compiled a list of the entire situation. I
would appreciate your guidance.
On the 2014-06-17, due to a security issues, the S3 bucket was 'uncleanly'
unmounted.
fsck logs shows this:
2013-01-03 10:31:54.990 [4609] MainThread: [fsck] Compressing and uploading
metadata...
2013-05-09 02:21:07.894 [1575] MainThread: [fsck] Compressing and uploading
metadata...
2013-06-28 13:08:22.494 [701] MainThread: [fsck] Compressing and uploading
metadata...
2013-07-01 10:14:16.153 [2074] MainThread: [fsck] Compressing and uploading
metadata...
The drive has been mounted since 2013-07-01. The S3 drive and server were
working just fine
The mount log is showing this:
2013-11-09 10:31:29.104 [2342] Metadata-Upload-Thread: [mount] Remote
metadata is newer than local (26 vs 25), refusing to overwrite!
2013-11-10 10:31:38.927 [2342] Metadata-Upload-Thread: [mount] Remote
metadata is newer than local (26 vs 25), refusing to overwrite!
........
........
2014-06-15 12:16:13.219 [2342] Metadata-Upload-Thread: [mount] Remote
metadata is newer than local (26 vs 25), refusing to overwrite!
2014-06-16 12:16:29.444 [2342] Metadata-Upload-Thread: [mount] Remote
metadata is newer than local (26 vs 25), refusing to overwrite!
I have a backup of local metadata before the reboot:
178565120 Jun 17 08:15 s3:=2F=2F3273a750-49d0-11e2-98bf-x=2F.db
28672 Jun 17 08:20 s3:=2F=2F3273a750-49d0-11e2-98bf-x=2F-cache
s3qladm download-metadata shows this:
The following backups are available:
No Name Date
0 s3ql_metadata_bak_0 2013-07-02 11:14:55
1 s3ql_metadata_bak_1 2013-07-01 11:14:14
2 s3ql_metadata_bak_10 2013-06-24 03:34:58
3 s3ql_metadata_bak_2 2013-07-01 03:20:06
4 s3ql_metadata_bak_3 2013-06-30 03:19:49
5 s3ql_metadata_bak_4 2013-06-29 03:13:52
6 s3ql_metadata_bak_5 2013-06-28 14:08:21
7 s3ql_metadata_bak_6 2013-06-28 03:36:40
8 s3ql_metadata_bak_7 2013-06-27 03:36:20
9 s3ql_metadata_bak_8 2013-06-26 03:35:40
10 s3ql_metadata_bak_9 2013-06-25 03:35:20
When I run mount I get this message:
mount.s3ql --debug all --allow-other s3://3273a750-49d0-11e2-98bf-x/
/production/
Using 4 upload threads.
Ignoring locally cached metadata (outdated).
Backend reports that fs is still mounted elsewhere, aborting.
the log shows this:
2014-06-20 11:11:11.285 [2810] MainThread: [mount] Using 4 upload threads.
2014-06-20 11:11:11.296 [2810] MainThread: [backend] Connecting to
3273a750-49d0-11e2-98bf-x.s3.amazonaws.com...
2014-06-20 11:11:11.296 [2810] MainThread: [backends.s3c] _do_request():
start with parameters ('GET', '/s3ql_passphrase', None, None, None, None)
2014-06-20 11:11:11.297 [2810] MainThread: [backends.s3c] _send_request():
processing request for /s3ql_passphrase
2014-06-20 11:11:11.499 [2810] MainThread: [backends.s3c] _do_request():
request-id: 9CDA025F6097B7AA
2014-06-20 11:11:11.499 [2810] MainThread: [backend] Connecting to
3273a750-49d0-11e2-98bf-x.s3.amazonaws.com...
2014-06-20 11:11:11.500 [2810] MainThread: [backends.s3c]
list(s3ql_seq_no_): start
2014-06-20 11:11:11.500 [2810] MainThread: [backends.s3c]
list(s3ql_seq_no_): requesting with marker=
2014-06-20 11:11:11.500 [2810] MainThread: [backends.s3c] _do_request():
start with parameters ('GET', '/', None, {'marker': '', 'prefix':
's3ql_seq_no_', 'max-keys': 1000}, None, None)
2014-06-20 11:11:11.500 [2810] MainThread: [backends.s3c] _send_request():
processing request for /?marker=&prefix=s3ql_seq_no_&max-keys=1000
2014-06-20 11:11:11.976 [2810] MainThread: [backends.s3c] _do_request():
request-id: 5D9137F85B03A508
2014-06-20 11:11:11.977 [2810] MainThread: [backends.s3c]
lookup(s3ql_seq_no_32)
2014-06-20 11:11:11.977 [2810] MainThread: [backends.s3c] _do_request():
start with parameters ('HEAD', '/s3ql_seq_no_32', None, None, None, None)
2014-06-20 11:11:11.977 [2810] MainThread: [backends.s3c] _send_request():
processing request for /s3ql_seq_no_32
2014-06-20 11:11:12.081 [2810] MainThread: [backends.s3c] _do_request():
request-id: BC7B2A1E47957299
2014-06-20 11:11:12.082 [2810] MainThread: [backends.s3c]
lookup(s3ql_seq_no_32)
2014-06-20 11:11:12.082 [2810] MainThread: [backends.s3c] _do_request():
start with parameters ('HEAD', '/s3ql_seq_no_32', None, None, None, None)
2014-06-20 11:11:12.082 [2810] MainThread: [backends.s3c] _send_request():
processing request for /s3ql_seq_no_32
2014-06-20 11:11:12.187 [2810] MainThread: [backends.s3c] _do_request():
request-id: 6523713EB5C6A260
2014-06-20 11:11:12.187 [2810] MainThread: [backends.s3c]
lookup(s3ql_seq_no_33)
2014-06-20 11:11:12.187 [2810] MainThread: [backends.s3c] _do_request():
start with parameters ('HEAD', '/s3ql_seq_no_33', None, None, None, None)
2014-06-20 11:11:12.188 [2810] MainThread: [backends.s3c] _send_request():
processing request for /s3ql_seq_no_33
2014-06-20 11:11:12.293 [2810] MainThread: [backends.s3c] _do_request():
request-id: AA33A907680CDB76
2014-06-20 11:11:12.294 [2810] MainThread: [mount] Ignoring locally cached
metadata (outdated).
2014-06-20 11:11:12.294 [2810] MainThread: [backends.s3c]
lookup(s3ql_metadata)
2014-06-20 11:11:12.294 [2810] MainThread: [backends.s3c] _do_request():
start with parameters ('HEAD', '/s3ql_metadata', None, None, None, None)
2014-06-20 11:11:12.295 [2810] MainThread: [backends.s3c] _send_request():
processing request for /s3ql_metadata
2014-06-20 11:11:12.421 [2810] MainThread: [backends.s3c] _do_request():
request-id: 7ACC8A402E8CD652
2014-06-20 11:11:12.421 [2810] MainThread: [root] Backend reports that fs
is still mounted elsewhere, aborting.
So I goto run fsck.s3ql
fsck.s3ql s3://3273a750-49d0-11e2-98bf-x/
Starting fsck of s3://3273a750-49d0-11e2-98bf-x/
Ignoring locally cached metadata (outdated).
Backend reports that file system is still mounted elsewhere. Either
the file system has not been unmounted cleanly or the data has not yet
propagated through the backend. In the later case, waiting for a while
should fix the problem, in the former case you should try to run fsck
on the computer where the file system has been mounted most recently.
Enter "continue" to use the outdated data anyway:
> quit
I find the combination of these comments confused me (I'm a bit slow:)
"Ignoring locally cached metadata (outdated)" and "Enter "continue" to use
the outdated data anyway". To me this suggests it's going to use 'outdated'
date, which it already identified as locally cached. Unless both the
locally cached metadata is (outdated) and the remote data is outdated,
compared to what?
So, I am confused as how to proceed. Right now I have the options
A) Run fsck.s3ql and Enter "continue" to use the outdated data anyway.
B) Apply your patch and force the local metadata to be used.
Please, any assistance is greatly appreciated.
--
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 s3ql+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
