Nuno Lucas-2 wrote: > > On 5/23/07, Shilpa Sheoran <sheoran.shi...@gmail.com> wrote: >> Linux 2.6.9 >> and the media is Nand Flash memory. >> /dir1/dir2/dir3 >> >> /dir1/dir2 is readonly (cramfs) >> dir3 is read write (Flash mem). and I'm creating the database in dir3. > > There is your problem. The file system on that directory (I would > guess JFS2 or similar), doesn't support the fsync() call. > > This might not be true. See below: http://www.linux-mtd.infradead.org/faq/jffs2.html " On NOR FLASH each write goes directly into the FLASH.
On NAND FLASHM and NOR ECC FLASH we have a write-buffer for writing only full pages to the chips. There could be a loss of data, when the write-buffer is not flushed before power down. There are some mechanisms to ensure, that the write-buffer is flushed. You can force the flush of the write-buffer by using fsync() or sync() in your application. JFFS2 has a timed flush of the write buffer, which forces the flush of the buffer to flash, if there are no writes to the filesystem for more than about 5 seconds. The time depends on the cycle-time of kupdated, which can be adjusted via /proc/sys/vm/dirty_expire_centisecs." -- View this message in context: http://www.nabble.com/SQL-error%3A-disk-I-O-error-tp10729555p24008290.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
