> If you have only accessed the file system from one computer, the best
> course of action to get a consistent file system again would be to use
> the most-recent copy of the local metadata that you have, and force
> fsck.s3ql to use that in favor of the remote metadata using the
> following patch (no that this is slightly different than the patch I
> posted before):
>
> --- a/src/s3ql/fsck.py
> +++ b/src/s3ql/fsck.py
> @@ -1095,6 +1095,8 @@
> assert os.path.exists(cachepath + '.db')
> with open(cachepath + '.params', 'rb') as fh:
> param = pickle.load(fh)
> + log.warning('WARNING! Forcing use of local metadata!')
> + param['seq_no'] = seq_no+1
> if param['seq_no'] < seq_no:
> log.info('Ignoring locally cached metadata (outdated).')
> param = backend.lookup('s3ql_metadata')
>
> Thank you very much. That worked very well.
Changing the file back to it's original state now.
Thanks again.
--
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.
