FWIW, I used s3qladm download-metadata to download the second-most-recent metatdata, and the fskc ran successfully. -- with a bunch of like the following:
Deleted spurious object 299006 ... object 298984 only exists in table but not in backend, deleting ... WARNING: object 298991 only exists in table but not in backend, deleting But, once complete I was about to mount etc and resume use. Since the file system is a mirror/backup that occurs every hour, I am not particularly concerned with losing 2 hours, but I am very interested to know if this is the correct approach to have used, or if there are better approaches. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/s3ql/9d4d542b-c03c-46a2-b5a3-59fc76f617d1%40googlegroups.com.
