On Sunday, June 22, 2014 2:22:42 AM UTC+2, Nikolaus Rath wrote: > > PA Nilsson <[email protected] <javascript:>> writes: > > So my thinking is that this is a problem that we have with our flash > based > > file system. The file is simply not yet written to flash. > > This will be running on an "non maintained" system with no possibility > for > > user interaction. > > If there is a high chance that the system will be power-cycled without a > proper shutdown, you may want to apply the following patch as swell (in > addition to the patch from my other mail). It reduces the likelyhood of > metadata data corruption on power loss, but also reduces performance (so > this is not going to go into the official S3QL code): > > diff --git a/src/s3ql/database.py b/src/s3ql/database.py > --- a/src/s3ql/database.py > +++ b/src/s3ql/database.py > @@ -32,7 +32,7 @@ > # locking_mode to EXCLUSIVE, otherwise we can't switch the > locking > # mode without first disabling WAL. > 'PRAGMA synchronous = OFF', > - 'PRAGMA journal_mode = OFF', > + 'PRAGMA journal_mode = NORMAL', > #'PRAGMA synchronous = NORMAL', > #'PRAGMA journal_mode = WAL', > > Thank you very much for your support Nikolaus. I finally found the time to test this, and I have not been able to reproduce the error after applying your patches.
/PA -- 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.
