On Tuesday, January 26, 2016 at 8:10:08 PM UTC+1, Cliff Stanford wrote: > > On 26/01/16 19:58, 'Igor Galić' via s3ql wrote: > > > split brain situations aren't theoretical. completely avoiding them > > is sometimes impossible. http://queue.acm.org/detail.cfm?id=2655736 > > Sometimes you lose a machine because it's literally on fire, or just > > because its hard disk(s) breaks… > > Have you thought about setting --metadata-upload-interval to something > lower than the default 86,400? Maybe reduce it to 3,600 which means you > won's lose more than an hour's data. > > > Even just a shutdown of the vm (which, in theory, unmounts all file > systems) > > will make it so that it's impossible to mount the fs on another machine: > > Are you sure that the shutdown is (a) calling umount.s3ql and (b) >
probably not. Since it's mounted and not handled as service (yet), and we're calling shutdown, it'll just be unmounted using umount > waiting for it to finish? It can take a very long time to return, > and standard umount (or shutdown) might be a little impatient… > depending on the size of the dirty cache, the size of the metadata and > the speed of the line. > > but this sounds like a very good idea, and i'll try that out *now* > Regards > Cliff. > > -- > Cliff Stanford > Office: +44 20 0222 1666 UK Mobile: +44 7973 616 666 > Spain: +34 952 587 666 > http://www.may.be/ > -- 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.
