On 20 Sep 2011, at 1:46pm, Berthier, Emmanuel wrote: > From: sqlite-users-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Stephan Beal > >> ...barrier=1 and do not disable the write cache so most Linux distributions >> are vulnerable to this problem. Note that this is an operating system and >> hardware issue and that there is nothing that SQLite can do to work around >> it. Other database engines have also run into this same problem." >> >> But notice those last two sentences. > > The sentence starts with: > " We are told that most Linux distributions do not use barrier=1 and do not > disable the write cache so most Linux distributions are vulnerable to this > problem." > > I managed the FS mount option and this partition is mount write-back mode > with barrier=1.
Can I ask where a power failure or a crash is involved in your finding at all ? Or is the corruption found when programs have only ever run as designed with no unexpected termination ? I assume your app does sqlite3_close() in the expected manner. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
