=== ...you must fsync the containing directory... === Is there an Sqlite option to achieve that?
In fact, to summarise: Suppose I would like to maximise my chances of avoiding the 'Lost Post-It' problem described above. What are _all_ the Sqlite compile-time options, and their values, needed under Linux? (I appreciate the disk hard/firmware will need to be looked at as well) Best regards On Thu, Jan 28, 2016 at 4:37 PM, Howard Chu <hyc at symas.com> wrote: > Simon Slavin wrote: > >> >> On 28 Jan 2016, at 1:38pm, Bernard McNeill <bm.email01 at gmail.com> wrote: >> >> === >>> Like the user reading ?saving OK? and throwing away the >>> Post-It with the original information >>> === >>> >>> This is exactly my concern. >>> The user throwing away the Post-It is entirely reasonable if he sees a >>> message like that. >>> >>> Do you happen to know if Linux/Debian (which I think uses a journalling >>> filesystem) carries this risk? >>> >> >> The problem is not at the software level. >> > > Not true. There *is* a problem at the software level - on Linux, current > BSD (and apparently also on QNX) you must fsync the containing directory > when you make changes to the contents of a directory (create/delete/rename > files). This is above and beyond whatever lies the hardware layer may tell > you. It's a documented requirement in Linux, at least. It is also > independent of whether or not the filesystem uses journaling. > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >