Hello, In my setup, I use metadata-upload-interval=3600. Which means that the cached data is uploaded to the server every hour.
If anything goes wrong, the worst scenario is 1hour of written data lost. Regards. *Alexandre Gonçalves* ............................................................................................................................ Email: [email protected] 2016-04-18 12:41 GMT+01:00 Terada Michitaka <[email protected]>: > I tested s3ql filesystem. > Test script is below. > > 1. cp 100MB * 10 files to NFS mounted directory. > 2. ls that dir. > 3. rm all files(written in step 1.) > 4. return to step 1. > > After 1 day and half later, s3ql changed its state to "failsafe mode" with > this log. > --------- > 2016-04-14 08:50:29.585 4026:Metadata-Upload-Thread s3ql.mount.run: > Remote metadata is newer than local (22 vs 21), refusing to overwrite and > switching to failsafe mode! > --------- > > To prevent loosing data, I specified 10 seconds for > "metadata-upload-interval" mount option. > Is this interval too short? > What is the suitable value for "metadata-upload-interval" mount option? > > If the interval is changed longer value, occurrence frequency of this > state changing will probably be declining. > But this error will occur. It depends on timing. I think there is some > problem. > > Thanks. > > -- > 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. > -- 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.
