> > > Duh, no idea how that could possibly happen. Are you sure nothing > mount.s3ql can have touched the cache directory? >
Well, I'm pretty sure about this... As there is only s3ql and btsync running on this Amazon instance, nothing more. And btsync has nothing to do with those cache directories... > > If so, it'd be great if you could find a way for me to reproduce the > problem. Otherwise there's little I can do. > Ok fine, I will try! > At this point, you may have to delete the cache directory. That may > result in some data loss though. > Thanks for your help! After removing files inside cache directories I was able to run fsck.s3ql and then mount.s3ql. The buckets are fine, no data loss as I've set the upload metadata to 900sec. Anyway as soon as I will find some times, I will upgrade s3ql to v2.16... Hope it will solve this issue ;-) Have a good day! Regards. Jonathan -- 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.
