On 06/21/2014 07:03 PM, Warren Daly wrote:
>
>
> Please test the link before sending the next email.
>
>
> Sorry
>
> wget http://www.invisibleagent.com/mntfsk.tar
Too bad, these logs don't go back far enough. So there's no telling how
and when this problem began.
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')
To detect problems like this earlier, I'd recommend to use a tool like
logcheck to automatically scan the log files. That way, you get notified
if something unexpected happens (and hopefully before anything actually
breaks).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
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.
