I have a backup saving to a samba share backed by S3QL. The file "saves" successfully to the share and S3QL starts the upload to S3 as normal. After the save to the share completes a verify is run on the file, but this is where it fails. I understand the eventual consistency issues, so I enlarged the s3ql cache to exceed the size of the file being saved thinking that perhaps a portion of the file was out of cache and not yet being reported by S3 when being re-requested. I was wrong - it still fails. I can confirm the the S3QL cache is essentially the same size as the file being saved, so consistency should not be an issue as the file being requested should be coming from cache. If I allow time for the S3 upload to complete, and then manually run a verify only, the verify is successful. Due to the speed at which the verify is running confirms that the file is being read from cache and not S3. Any idea why the immediate verify after write is failing?
Thank you! -- 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.
