Warren Daly <[email protected]> writes:
> 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 probably did lose those objects that fsck deleted ([fsck] Deleted
> spurious object)
>
> 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.
>
> I know there is nothing else mounting, because I've just booted the
> instance. Investigating now.
> 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'):
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.
