>
> > Also reading up on how to not ignore local metadata?
>
> There is no easy way to do that. One way is to change fsck.py to pretend
> that the remote sequence number is zero. The following change will do
> that (make sure to revert it after use!):
>
> diff --git a/src/s3ql/fsck.py b/src/s3ql/fsck.py
> --- a/src/s3ql/fsck.py
> +++ b/src/s3ql/fsck.py
> @@ -1084,7 +1084,8 @@
> raise QuietError(str(exc))
>
> cachepath = get_backend_cachedir(options.storage_url,
> options.cachedir)
> - seq_no = get_seq_no(backend)
> + log.warning("**WARNING** IGNORING REMOTE METADATA")
> + seq_no = 0
> db = None
>
> if os.path.exists(cachepath + '.params'):
>
Well this is the log file before the reboot. it would appear that these
logs indicate that I should just use the remote metadata (and in turn allow
deletion of Spurious objects)?
The whole reason I have started this thread is anxiousness when it reports
deletion of so many "Spurious objects". To put things in perspective there
is about 360,000 files on the system. Fsck processes about 600,000 objects.
Then begins to delete "Spurious objects" one by one. I would prefer if it
moved them to Lost & Found or I could even move them to a specific folder.
2014-06-16 12:06:31.284 [2342] Dummy-27: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.open_read...
2014-06-16 12:06:36.354 [2342] Dummy-58: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.open_read...
2014-06-16 12:14:22.142 [2342] Thread-4: [backend] Encountered
BadStatusLine exception (''), retrying call to ObjectW.close...
2014-06-16 12:14:22.228 [2342] Thread-16: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.delete...
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!
2014-06-16 12:19:32.735 [2342] Dummy-45: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.open_read...
2014-06-16 12:28:24.510 [2342] Thread-5: [backend] Encountered error
exception ([Errno 110] Connection timed out), retrying call to
ObjectW.close...
2014-06-16 12:34:52.656 [2342] Dummy-45: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.open_read...
2014-06-16 12:40:03.505 [2342] Thread-5: [backend] Encountered
BadStatusLine exception (''), retrying call to ObjectW.close...
2014-06-16 12:41:35.650 [2342] Dummy-27: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.open_read...
2014-06-16 12:41:35.669 [2342] Dummy-21: [backend] Encountered
BadStatusLine exception (''), retrying call to Backend.open_read...
--
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.
