Hi,
Was the system ever restarted since 2013-07-02? - No it was not
Was the file system ever unmounted since 2013-07-02? - No, it was never
unmounted, until just before rebooting.
How are you starting mount.s3ql? I use #mount.s3ql --allow-other
s3://xxxxxxxxxxxxx/ /folder/
Are you using the --metadata-upload-interval option? - No, so I'm relying
on the 24Hr default.
The mount.log.5 is the oldest file I have
2013-12-18 10:38:26.281 [2342] Metadata-Upload-Thread: [mount] Dumping
metadata...
2013-12-18 10:38:26.282 [2342] Metadata-Upload-Thread: [metadata]
..objects..
2013-12-18 10:38:28.706 [2342] Metadata-Upload-Thread: [metadata] ..blocks..
2013-12-18 10:38:29.969 [2342] Metadata-Upload-Thread: [metadata] ..inodes..
2013-12-18 10:38:33.473 [2342] Metadata-Upload-Thread: [metadata]
..inode_blocks..
2013-12-18 10:38:36.842 [2342] Metadata-Upload-Thread: [metadata]
..symlink_targets..
2013-12-18 10:38:36.843 [2342] Metadata-Upload-Thread: [metadata] ..names..
2013-12-18 10:38:37.183 [2342] Metadata-Upload-Thread: [metadata]
..contents..
2013-12-18 10:38:38.860 [2342] Metadata-Upload-Thread: [metadata]
..ext_attributes..
2013-12-18 10:38:38.897 [2342] Metadata-Upload-Thread: [backends.s3c]
Encountered BadStatusLine exception (''), retrying call to
s3c.Backend.list()
2013-12-18 10:38:39.945 [2342] Metadata-Upload-Thread: [mount] Remote
metadata is newer than local (26 vs 25), refusing to overwrite!
So the system was mounted in 2013, never rebooted, or unmounted. The system
was accessing files perfectly fine on the remote S3 system.
Last week I umounted and rebooted.
Now I need to figure out if the remote metadata is newer or the local data.
Any assistance is appreciated.
Regards,
Warren
--
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.
