Dear Nikoluas, thank you for your time and effort to reply. I really appreciate you help. Thank you.
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 one I was using is 48Mb, but the one I have from 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... and I'm pretty certain it will start to "delete spurious objects" 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 made a backup of all of these (even thought they are a year old) 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 Should I use s3qlctrl to upload the 178Mb localmeta data files? then mount or fsck and mount? 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.
