On Mon, May 27, 2013 at 11:33:08AM -0400, Richard Hipp wrote: > On Mon, May 27, 2013 at 11:22 AM, Woody Wu <narkewo...@gmail.com> wrote: > > > Richard, > > > > If Yaffs2 is the cause, how can I write an effective test to exposure it? > > > > Do you really need to prove that yaffs2 is at fault? Try this experiment: > mention that you might be having problems with yaffs2 to anybody else who > has done a lot of work with yaffs2 and watch them nod knowingly....
Hope I can shot their nods and send pictures to my boss :) > > Android switched from yaffs2 to ext4 for a reason, you know. > > Another thing is very suspicious: after a while of running the test > > program, I can see from my syslog that there are a log of warning messages, > > something like: Yaffs2 trunk nnnn was not erased. On one hand, I am not > > sure if this is caused by sqlite or Yaffs2 itself, on the other hand, I > > also cannot prove this really means bad things since the program at that > > moment was still running fine. > > > > SQLite never writes to the system log. And even if it did, SQLite does not > know what filesystem it is talking to. Hence, any messages you see in the > system log that mention "yaffs2" are very likely coming from yaffs2 itself. > > I'm thinking you need to take a clue from the (very smart and very capable) > Android team and change to ext4 on your embedded system. > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- woody I can't go back to yesterday - because I was a different person then. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
