Dear Nikoluas,
thank you for your time and effort to reply. I really appreciate your help.
Thank you.
I am using S3QL 1.12
To recap:
I have a backup of what I believe is good local metadata.
I can't mount the S3 volume because it's say it's mounted elsewhere (it's
not)
I run fsck. fsck asks me to ignore local data... it downloads metadata (but
which date? from where I don't know)
Then it will start to delete spurious objects. I guess I could leave this
run... but it makes me very nervous. Why delete so many objects?
A general question, under normal operations, What does fsck mean when it
says "[fsck] Deleted spurious object"
is it removing items on the S3 drive that are no longer in the local
metadata file?
Ok I have a backup of the local metadata - the backup is 178Mb (.db) file.
So I placed the backup of the .db and params file in the .s3ql folder.
When I run:
mount.s3ql --allow-other s3:/xxxx/ /folder/
I see this in the mount.log file:
2014-06-18 12:52:07.928 [2980] MainThread: [mount] Using 4 upload threads.
2014-06-18 12:52:08.669 [2980] MainThread: [mount] Ignoring locally cached
metadata (outdated).
2014-06-18 12:52:08.772 [2980] MainThread: [root] Backend reports that fs
is still mounted elsewhere, aborting.
When I run fsck.s3ql s3://xxxxx/ I see this:
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:
here is the log before I killed the process.
It downloads a replaces the local 178Mb copy with a 48Mb db... (not sure
the date of the file it downloads)
I killed it because it's delete spurious objects. And I'm afraid something
has gone wrong (but it might not have!) I'm just being overly cautious.
fsck.log
2014-06-18 13:09:33.264 [4039] MainThread: [fsck] Ignoring locally cached
metadata (outdated).
2014-06-18 13:09:49.719 [4039] MainThread: [fsck] Downloading and
decompressing metadata...
2014-06-18 13:09:52.733 [4039] MainThread: [fsck] Reading metadata...
2014-06-18 13:09:52.735 [4039] MainThread: [metadata] ..objects..
2014-06-18 13:09:55.099 [4039] MainThread: [metadata] ..blocks..
2014-06-18 13:09:58.414 [4039] MainThread: [metadata] ..inodes..
2014-06-18 13:10:01.647 [4039] MainThread: [metadata] ..inode_blocks..
2014-06-18 13:10:04.515 [4039] MainThread: [metadata] ..symlink_targets..
2014-06-18 13:10:04.516 [4039] MainThread: [metadata] ..names..
2014-06-18 13:10:05.774 [4039] MainThread: [metadata] ..contents..
2014-06-18 13:10:09.780 [4039] MainThread: [metadata] ..ext_attributes..
2014-06-18 13:10:11.354 [4039] MainThread: [fsck] Creating temporary extra
indices...
2014-06-18 13:10:12.770 [4039] MainThread: [fsck] Checking lost+found...
2014-06-18 13:10:12.771 [4039] MainThread: [fsck] Checking cached objects...
I have also made a backup of all of these (even thought they are a year old)
s3qladm shows these:
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
But the log files showing this everyday....
2014-06-15 12:15:55.990 [2342] Metadata-Upload-Thread: [mount] Dumping
metadata...
2014-06-15 12:15:55.991 [2342] Metadata-Upload-Thread: [metadata]
..objects..
2014-06-15 12:15:59.171 [2342] Metadata-Upload-Thread: [metadata] ..blocks..
2014-06-15 12:16:04.010 [2342] Metadata-Upload-Thread: [metadata] ..inodes..
2014-06-15 12:16:08.287 [2342] Metadata-Upload-Thread: [metadata]
..inode_blocks..
2014-06-15 12:16:10.250 [2342] Metadata-Upload-Thread: [metadata]
..symlink_targets..
2014-06-15 12:16:10.251 [2342] Metadata-Upload-Thread: [metadata] ..names..
2014-06-15 12:16:10.899 [2342] Metadata-Upload-Thread: [metadata]
..contents..
2014-06-15 12:16:12.456 [2342] Metadata-Upload-Thread: [metadata]
..ext_attributes..
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:13.241 [2342] Metadata-Upload-Thread: [mount] Dumping
metadata...
2014-06-16 12:16:13.242 [2342] Metadata-Upload-Thread: [metadata]
..objects..
2014-06-16 12:16:16.184 [2342] Metadata-Upload-Thread: [metadata] ..blocks..
2014-06-16 12:16:20.735 [2342] Metadata-Upload-Thread: [metadata] ..inodes..
2014-06-16 12:16:25.037 [2342] Metadata-Upload-Thread: [metadata]
..inode_blocks..
2014-06-16 12:16:26.751 [2342] Metadata-Upload-Thread: [metadata]
..symlink_targets..
2014-06-16 12:16:26.751 [2342] Metadata-Upload-Thread: [metadata] ..names..
2014-06-16 12:16:27.395 [2342] Metadata-Upload-Thread: [metadata]
..contents..
2014-06-16 12:16:28.727 [2342] Metadata-Upload-Thread: [metadata]
..ext_attributes..
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'm confused s3qladm shows backups that are a year old!
But the log files show that the remote metadata is 'newer' than the local?
How can i download this remote metadata that is newer?
Please, any guidance is welcome.
--
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.
