|
|
@@ -703,7 +703,7 @@ int do_zflush(passdb_context *ctx, void *data, int len)
|
|
|
//In fast mode, we apply all of our update to the memory window without calling msync() or write(), and then
|
|
|
//(see below) when we're done rewriting the mmap()'d window for the local database, then we make one call
|
|
|
//to msync() or write() and splat it all down to flash at once. This gets us a better compression ratio
|
|
|
- //on the large chunks of file (like the Cornell passes) which change infrequently and it produces less
|
|
|
+ //on the large chunks of file which change infrequently and it produces less
|
|
|
//filesystem fragmentation, but it means that it is theoretically possible for a power event to cause a
|
|
|
//partial write to corrupt the local database (requiring a new flush). That being said, when running on
|
|
|
//top of JFFS2, this should cause file truncation, which will be easily detectable and trigger another
|